Triple
T36706105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight 1st Class |
E906363
|
entity |
| Predicate | statusWithinOrder |
P200854
|
FINISHED |
| Object | intermediate grade |
—
|
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: intermediate grade | Statement: [Knight 1st Class, statusWithinOrder, intermediate grade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusWithinOrder Context triple: [Knight 1st Class, statusWithinOrder, intermediate grade]
-
A.
orderWithin
Indicates that one entity is positioned or ranked before or after another entity within a defined sequence or ordering.
-
B.
order66Status
Indicates the status or condition of an entity with respect to the execution or enforcement of Order 66.
-
C.
positionOnOrder
Indicates the specific placement or sequence of an item within an ordered list or collection.
-
D.
establishedWithinOrder
Indicates that one entity was founded, created, or formally established as part of, or under the authority of, a particular order or organizational structure.
-
E.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
| PDg | Predicate description generation | batch_69ffb1f001948190a63c493b596a97b9 |
completed | May 9, 2026, 10:15 p.m. |
Created at: May 3, 2026, 4:12 p.m.