Triple
T19812890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Troyes |
E475988
|
entity |
| Predicate | approvedVowsOf |
P89916
|
FINISHED |
| Object | poverty for Knights Templar |
—
|
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: poverty for Knights Templar | Statement: [Council of Troyes, approvedVowsOf, poverty for Knights Templar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedVowsOf Context triple: [Council of Troyes, approvedVowsOf, poverty for Knights Templar]
-
A.
vowsTo
Indicates a commitment or solemn promise made by one entity to another to perform, uphold, or refrain from specific actions.
-
B.
fulfilledVow
Indicates that an entity has carried out or honored a previously made vow or promise.
-
C.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
D.
associatedVow
chosen
Indicates a relationship where a vow is linked or connected to a particular entity or event.
-
E.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542d7c048190818359cbf430f50e |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.