Triple
T23781487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalu River Broken Bridge |
E587825
|
entity |
| Predicate | yearOfMajorDestruction |
P53685
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [Yalu River Broken Bridge, yearOfMajorDestruction, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfMajorDestruction Context triple: [Yalu River Broken Bridge, yearOfMajorDestruction, 1950]
-
A.
destroyedCityYear
Indicates that a specific city was destroyed in a particular year.
-
B.
firstBuildingDestructionDate
Indicates the date on which the first instance of a building’s destruction occurred in the given context or sequence of events.
-
C.
timePeriodOfMajorDestruction
Indicates the time span during which a major destructive event affecting the subject occurred.
-
D.
sufferedDestructionIn
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
E.
yearOfDestruction
chosen
Indicates the specific year in which an entity was destroyed or ceased to exist.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62d7c608190b5fd0cf35f5faf42 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.