Triple
T2545827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loop transportation system |
E57898
|
entity |
| Predicate | involvesConstructionActivity |
P39476
|
FINISHED |
| Object | tunnel boring |
—
|
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: tunnel boring | Statement: [Loop transportation system, involvesConstructionActivity, tunnel boring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesConstructionActivity Context triple: [Loop transportation system, involvesConstructionActivity, tunnel boring]
-
A.
constructionLabor
Indicates a relationship where an entity performs or provides labor specifically for construction-related work or projects.
-
B.
constructionSite
Indicates that an entity is a location or area where construction work is actively taking place or is planned to occur.
-
C.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
D.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
E.
constructionType
Indicates the specific method or style by which something is built or constructed.
- F. None of above. chosen
Provenance (4 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2c285288190b41fc0188879623a |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.