Triple
T18657754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templars’ Tunnel |
E456110
|
entity |
| Predicate | discoveryCause |
P87882
|
FINISHED |
| Object | sewage blockage repair work |
—
|
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: sewage blockage repair work | Statement: [Templars’ Tunnel, discoveryCause, sewage blockage repair work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryCause Context triple: [Templars’ Tunnel, discoveryCause, sewage blockage repair work]
-
A.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
causeOfDiscovery
chosen
Indicates that one entity is the reason or factor that led to the discovery of another entity.
-
D.
disappearanceCause
Indicates the reason or factor that led to an entity’s disappearance.
-
E.
displacementCause
Indicates a causal relationship where one entity is responsible for the displacement or forced movement of another entity from its original location or situation.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e550864b0481909e59fbcc79fda839 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.