Triple
T26844636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Montferrat |
E675882
|
entity |
| Predicate | associatedWithCrusade |
P86914
|
FINISHED |
| Object | Second Crusade |
—
|
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: Second Crusade | Statement: [Marquess of Montferrat, associatedWithCrusade, Second Crusade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCrusade Context triple: [Marquess of Montferrat, associatedWithCrusade, Second Crusade]
-
A.
notableCrusade
chosen
Indicates that an entity is significantly associated with, or distinguished for its involvement in, a particular Crusade.
-
B.
targetOfCrusade
Indicates that an entity is the object or intended objective of a crusade or crusading campaign.
-
C.
roleAtCrusaders
Indicates the specific position, function, or capacity an entity holds within the Crusaders organization or group.
-
D.
associatedWithAntiCaliph
Indicates a relationship in which an entity is connected or linked to an anti-caliph, typically through support, affiliation, or involvement.
-
E.
crusadeNumber
Indicates the specific numbered iteration or sequence position of a crusade within a series of crusades.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: April 27, 2026, 5:10 a.m.