Triple
T532778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCSI |
E12258
|
entity |
| Predicate | partOfHonoursSystem |
P12022
|
FINISHED |
| Object | British honours system |
—
|
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: British honours system | Statement: [GCSI, partOfHonoursSystem, British honours system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfHonoursSystem Context triple: [GCSI, partOfHonoursSystem, British honours system]
-
A.
belongsToHonoursSystem
chosen
Indicates that something is a component or member of a specific honours or awards system.
-
B.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
C.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
D.
honourSystem
Indicates a relationship where compliance, access, or behavior is governed by trust in individuals to act honestly without direct enforcement or verification.
-
E.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.