Triple
T10041640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archer Artillery System |
E205308
|
entity |
| Predicate | loadingSystem |
P25802
|
FINISHED |
| Object | automatic |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: automatic | Statement: [Archer Artillery System, loadingSystem, automatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadingSystem Context triple: [Archer Artillery System, loadingSystem, automatic]
-
A.
loadingMechanism
chosen
Indicates the method or system by which something is loaded into or onto another object or structure.
-
B.
loadType
Indicates the manner or category of how something is loaded, such as the method, configuration, or type of loading applied in a given context.
-
C.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
D.
cargoSystem
Indicates a relationship where an entity is part of, managed by, or associated with a cargo-handling or cargo-management system.
-
E.
mountSystem
Indicates attaching a filesystem or storage resource to a system so that it becomes accessible for use.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:55 p.m.