Triple
T285028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman legion |
E5868
|
entity |
| Predicate | hasEngineeringCapability |
P3047
|
FINISHED |
| Object | road building |
—
|
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: road building | Statement: [Roman legion, hasEngineeringCapability, road building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringCapability Context triple: [Roman legion, hasEngineeringCapability, road building]
-
A.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
C.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
D.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
E.
hasAdvancedTechnologySector
Indicates that an entity possesses or includes a developed sector focused on advanced or high-tech industries, products, or services.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.