Triple
T11823668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames Tunnel |
E281201
|
entity |
| Predicate | hasConstructionProblem |
P12940
|
FINISHED |
| Object | financial difficulties |
—
|
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: financial difficulties | Statement: [Thames Tunnel, hasConstructionProblem, financial difficulties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionProblem Context triple: [Thames Tunnel, hasConstructionProblem, financial difficulties]
-
A.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
B.
hasPlanningIssue
Indicates that an entity is associated with a problem, concern, or complication related to planning or plan formulation.
-
C.
hadIssue
Indicates that an entity experienced, encountered, or was affected by a particular problem, defect, or difficulty.
-
D.
haveReconstructionWork
Indicates that an entity is undergoing or is associated with reconstruction or restoration work.
-
E.
constructionChallenges
chosen
Indicates difficulties, obstacles, or complications encountered during the process of constructing or building something.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.