Triple
T1203403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knights Companion of the Order of the Garter |
E25832
|
entity |
| Predicate | stallMarkedBy |
P25533
|
FINISHED |
| Object | knight's banner |
—
|
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: knight's banner | Statement: [Knights Companion of the Order of the Garter, stallMarkedBy, knight's banner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stallMarkedBy Context triple: [Knights Companion of the Order of the Garter, stallMarkedBy, knight's banner]
-
A.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
B.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
C.
suspendedBy
Indicates that one entity has temporarily halted, removed, or placed another entity in an inactive or pending state, typically as an enforcement or administrative action.
-
D.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
E.
mintMarkUsedOn
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
- F. None of above. chosen
Provenance (4 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdbf94188190991f63a84cc76b8a |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bcc82e38819081c3615e1cc7a66f |
completed | March 1, 2026, 10:25 p.m. |
Created at: March 1, 2026, 7:46 p.m.