Triple
T31428465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman military institutions |
E801729
|
entity |
| Predicate | hasLogisticalElement |
P87177
|
FINISHED |
| Object | military roads |
—
|
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: military roads | Statement: [Roman military institutions, hasLogisticalElement, military roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogisticalElement Context triple: [Roman military institutions, hasLogisticalElement, military roads]
-
A.
hasLogisticalRole
Indicates that an entity holds a responsibility or function related to planning, coordinating, or managing logistical operations or resources.
-
B.
logisticalCharacteristic
Indicates the logistical properties or constraints associated with an entity, such as how it is stored, transported, handled, or supplied.
-
C.
logisticsFeature
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
D.
logisticalEffect
Indicates the impact that one event, action, or condition has on the planning, coordination, or execution of logistical operations.
-
E.
hasTransportationElement
chosen
Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 30, 2026, 8:55 p.m.