Triple
T3103377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Founding of the Order of the Garter |
E64772
|
entity |
| Predicate | hasTypeOfOrder |
P1802
|
FINISHED |
| Object | order of chivalry |
—
|
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: order of chivalry | Statement: [Founding of the Order of the Garter, hasTypeOfOrder, order of chivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfOrder Context triple: [Founding of the Order of the Garter, hasTypeOfOrder, order of chivalry]
-
A.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
orderType
chosen
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
-
E.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26f376c8190a049399e33314d52 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.