Triple
T5260603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ai |
E118812
|
entity |
| Predicate | methodOfKingExecution |
P2115
|
FINISHED |
| Object | hanging on a tree |
—
|
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: hanging on a tree | Statement: [Battle of Ai, methodOfKingExecution, hanging on a tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfKingExecution Context triple: [Battle of Ai, methodOfKingExecution, hanging on a tree]
-
A.
executioner
Indicates that one entity performs or is responsible for carrying out an execution on another entity.
-
B.
usedMethodOfKilling
chosen
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
C.
finalSinkingMethod
Indicates the method or process ultimately used to sink or deliberately submerge an object, typically a vessel or structure.
-
D.
placeOfExecution
Indicates the location where an execution or carrying out of a sentence, order, or legal punishment took place.
-
E.
spouseExecutionMethod
Indicates the method by which a person's spouse was executed.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcf026c8190881b6e14b962a3c9 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.