Triple
T26527438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courtenay |
E670729
|
entity |
| Predicate | memberOfCrusaderNobility |
P125543
|
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: [Courtenay, memberOfCrusaderNobility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfCrusaderNobility Context triple: [Courtenay, memberOfCrusaderNobility, yes]
-
A.
roleAtCrusaders
Indicates the specific position, function, or capacity an entity holds within the Crusaders organization or group.
-
B.
associatedWithNobleOrder
chosen
Indicates that an entity has a formal or recognized connection to a noble order, such as membership, affiliation, or honorary association.
-
C.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
D.
hasPrimaryCrusaderLeader
Indicates that an entity (such as a crusade or crusading force) is associated with a specific individual who serves as its main or principal crusader leader.
-
E.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 1:33 a.m.