Triple
T4158899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Crusade |
E91481
|
entity |
| Predicate | originalObjective |
P50644
|
FINISHED |
| Object | reconquest of Jerusalem |
—
|
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: reconquest of Jerusalem | Statement: [Fourth Crusade, originalObjective, reconquest of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalObjective Context triple: [Fourth Crusade, originalObjective, reconquest of Jerusalem]
-
A.
objectiveIncludes
Indicates that a broader objective encompasses or contains a specific sub-objective, component, or element as part of its scope.
-
B.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
C.
originalPlan
chosen
Indicates that one entity is the initial or primary plan or intended course of action associated with another entity.
-
D.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
E.
originalMeaning
Indicates that something retains or conveys its initial, intended sense or significance, as opposed to a later or altered interpretation.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.