Triple
T4532501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Harran (1104) |
E106329
|
entity |
| Predicate | durationOfCaptivityForBaldwinII |
P50041
|
FINISHED |
| Object | approximately 4 years |
—
|
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: approximately 4 years | Statement: [Battle of Harran (1104), durationOfCaptivityForBaldwinII, approximately 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: durationOfCaptivityForBaldwinII Context triple: [Battle of Harran (1104), durationOfCaptivityForBaldwinII, approximately 4 years]
-
A.
reignAsKingOfJerusalemEnd
Indicates the point in time or event at which an individual’s reign as king of Jerusalem comes to an end.
-
B.
periodOfCaptivity
chosen
Indicates a time span during which an entity is held in captivity or confinement.
-
C.
resultOfSixthCrusade
Indicates that something occurs as a consequence or outcome of the events or agreements associated with the Sixth Crusade.
-
D.
reignAsKingOfJerusalemStart
Indicates the time at which an individual begins their reign as king of Jerusalem.
-
E.
lostJerusalemYear
Indicates the specific year in which the referenced party lost control of Jerusalem.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579f27ac8190ae9a4252109e56e1 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.