Triple
T18702996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond of Saint-Gilles |
E457297
|
entity |
| Predicate | pledgedVow |
P101277
|
FINISHED |
| Object | crusading vow to liberate 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: crusading vow to liberate Jerusalem | Statement: [Raymond of Saint-Gilles, pledgedVow, crusading vow to liberate Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pledgedVow Context triple: [Raymond of Saint-Gilles, pledgedVow, crusading vow to liberate Jerusalem]
-
A.
fulfilledVow
Indicates that an entity has carried out or honored a previously made vow or promise.
-
B.
vowsTo
Indicates a commitment or solemn promise made by one entity to another to perform, uphold, or refrain from specific actions.
-
C.
primaryVows
Indicates that an entity has made or is bound by its main or foundational vows, promises, or commitments in a given context.
-
D.
takesVowsOf
chosen
Indicates that an entity formally commits to specific vows, promises, or oaths, typically within a religious, ceremonial, or institutional context.
-
E.
pledgedByOthers
Indicates that a commitment, promise, or pledge toward an entity is made by parties other than the primary or focal entity.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56714d0588190ac050356bc2784fd |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.