Triple
T29860268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franks of the Levant |
E758291
|
entity |
| Predicate | finalMajorStrongholdLossYear |
P43678
|
FINISHED |
| Object | 1291 |
—
|
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: 1291 | Statement: [Franks of the Levant, finalMajorStrongholdLossYear, 1291]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMajorStrongholdLossYear Context triple: [Franks of the Levant, finalMajorStrongholdLossYear, 1291]
-
A.
yearDefeated
Indicates the specific year in which one entity defeated or overcame another in a competitive or conflict-related context.
-
B.
dateOfMilitaryDefeat
Indicates the specific date on which a military force or entity was defeated in a conflict or battle.
-
C.
dateOfMajorDefeat
chosen
Indicates the specific date on which an entity experienced a significant or decisive defeat.
-
D.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
E.
battleEndYear
Indicates the calendar year in which a particular battle or military engagement concluded.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 29, 2026, 5:48 p.m.