Triple
T2452564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Bell |
E53738
|
entity |
| Predicate | crackCause |
P694
|
FINISHED |
| Object | metal fatigue |
—
|
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: metal fatigue | Statement: [Liberty Bell, crackCause, metal fatigue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crackCause Context triple: [Liberty Bell, crackCause, metal fatigue]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
C.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
D.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
E.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:43 p.m.