Triple
T3178880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight Grand Commander |
E66530
|
entity |
| Predicate | entitlesHolderTo |
P41897
|
FINISHED |
| Object | title "Sir" |
—
|
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: title "Sir" | Statement: [Knight Grand Commander, entitlesHolderTo, title "Sir"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entitlesHolderTo Context triple: [Knight Grand Commander, entitlesHolderTo, title "Sir"]
-
A.
titleHolderTo
Indicates that one entity currently holds or possesses an official title, position, or designation in relation to another entity.
-
B.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of another entity.
-
C.
affectedTitleHolder
Indicates that a title holder is impacted or influenced in some way by a specified event, action, or relationship.
-
D.
titleHolderIs
chosen
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
E.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69db2088190baa1305892eb148a |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.