Triple
T15082642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gillespie Dam |
E360187
|
entity |
| Predicate | functionAfterFailure |
P9424
|
FINISHED |
| Object | local landmark |
—
|
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: local landmark | Statement: [Gillespie Dam, functionAfterFailure, local landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionAfterFailure Context triple: [Gillespie Dam, functionAfterFailure, local landmark]
-
A.
functionAfterSuppression
Indicates that one function or process occurs only after another has been suppressed or inhibited.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
laterFunction
chosen
Indicates that one function or event occurs after another in time.
-
D.
functionAfterConversion
Indicates that one function or behavior occurs as a result of, or is valid only after, a specified conversion has taken place.
-
E.
launchFailureMode
Indicates the specific way in which a launch attempt fails or the type of failure that occurs during a launch.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0027450a48190a84588b6aaf84ebf |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.