Triple
T29970113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sack of Luoyang |
E761291
|
entity |
| Predicate | capitalAttacked |
P176137
|
FINISHED |
| Object | Luoyang |
—
|
NE NERFINISHED |
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: Luoyang | Statement: [Sack of Luoyang, capitalAttacked, Luoyang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalAttacked Context triple: [Sack of Luoyang, capitalAttacked, Luoyang]
-
A.
capturedAttacker
Indicates that an entity has successfully apprehended or taken control of an attacking entity.
-
B.
wasAttackedIn
chosen
Indicates that an entity experienced an attack that occurred at or within a specified location or context.
-
C.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
D.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
E.
centralKnight
Indicates that a knight is positioned near the center of the board or central area in the given context.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 6:31 p.m.