Triple
T36433612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Zaragoza (778) |
E897508
|
entity |
| Predicate | outcomeForFranks |
P185746
|
FINISHED |
| Object | withdrawal without taking the city |
—
|
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: withdrawal without taking the city | Statement: [Siege of Zaragoza (778), outcomeForFranks, withdrawal without taking the city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForFranks Context triple: [Siege of Zaragoza (778), outcomeForFranks, withdrawal without taking the city]
-
A.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
outcomeForSarah
Indicates the result, consequence, or effect that a given situation, action, or event has specifically for Sarah.
-
C.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
-
D.
Rechtsfolge
Indicates the legal consequence or effect that follows from a specific legal condition, action, or rule.
-
E.
outcomeForManfred
Indicates the result, consequence, or effect that an event, action, or situation has specifically for Manfred.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.