Triple
T31762529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Antioch (272) |
E810719
|
entity |
| Predicate | cityRecapturedFrom |
P172275
|
FINISHED |
| Object | Palmyrene Empire |
—
|
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: Palmyrene Empire | Statement: [Siege of Antioch (272), cityRecapturedFrom, Palmyrene Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityRecapturedFrom Context triple: [Siege of Antioch (272), cityRecapturedFrom, Palmyrene Empire]
-
A.
cityRebuiltAfter
Indicates that a city was reconstructed or significantly restored following a prior event of destruction or severe damage.
-
B.
cityRebuiltBy
Indicates that a city has been reconstructed or significantly restored through the actions, efforts, or initiative of a specified agent or entity.
-
C.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
D.
cityHeld
Indicates that a particular city was the location where an event, activity, or occurrence took place or was hosted.
-
E.
citySacked
Indicates that a city has been violently attacked, looted, and destroyed or heavily damaged, typically as a result of military conquest.
- F. None of above. chosen
Provenance (4 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab81a81c81908236f2956569b4a8 |
completed | May 3, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:31 p.m.