Triple
T3870930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Dig |
E91982
|
entity |
| Predicate | majorConstructionCompletion |
P1511
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Big Dig, majorConstructionCompletion, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorConstructionCompletion Context triple: [Big Dig, majorConstructionCompletion, 2004]
-
A.
majorConstruction
Indicates a relationship where a construction project is large-scale, significant, or of primary importance in scope, impact, or resources.
-
B.
constructionCompleted
chosen
Indicates that a construction process or project has been fully finished and reached its completed state.
-
C.
majorConstructionUnder
Indicates that a location or structure is currently undergoing significant construction work or large-scale building activity.
-
D.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
-
E.
churchConstructionCompleted
Indicates that the process of building or constructing a church has been finished.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec54b0848190a8d4a0e4df7b6227 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.