Triple
T27145794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montferrat |
E681937
|
entity |
| Predicate | associatedWithCrusades |
P103797
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Montferrat, associatedWithCrusades, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCrusades Context triple: [Montferrat, associatedWithCrusades, yes]
-
A.
crusaderHistory
chosen
Indicates that an entity has a historical involvement, role, or association with the Crusades or crusading activities.
-
B.
roleDuringCrusades
Indicates the specific function, position, or involvement an entity had in relation to the Crusades during the period they occurred.
-
C.
associatedEmperorDuringFirstCrusade
Indicates a relationship where an entity is linked to the emperor who held authority or was prominently involved during the time of the First Crusade.
-
D.
targetOfCrusade
Indicates that an entity is the object or intended objective of a crusade or crusading campaign.
-
E.
countryDuringCrusades
Indicates that an entity functioned as or corresponded to a particular country during the historical period of the 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: April 27, 2026, 9:11 a.m.