Triple
T20152151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Member of the Order of the British Empire |
E491458
|
entity |
| Predicate | typicalLevelOfService |
P6199
|
FINISHED |
| Object | local level |
—
|
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: local level | Statement: [Member of the Order of the British Empire, typicalLevelOfService, local level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLevelOfService Context triple: [Member of the Order of the British Empire, typicalLevelOfService, local level]
-
A.
serviceLevel
chosen
Indicates the degree or quality of service provided or received in the relationship between entities.
-
B.
levelServed
Indicates that a particular service, function, or resource is provided or made available at a specified level or tier.
-
C.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
D.
typicalServiceRequirement
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
-
E.
typicalCommandLevel
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667dc34e081908e42e4c1bde26170 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.