Triple
T23674393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Gallantry Medal |
E584826
|
entity |
| Predicate | isNonOperational |
P2509
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [King’s Gallantry Medal, isNonOperational, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonOperational Context triple: [King’s Gallantry Medal, isNonOperational, true]
-
A.
isPartlyOperational
Indicates that an entity is functioning to some extent but not at full or normal operational capacity.
-
B.
doesNotOperate
chosen
Indicates that an entity is not functioning, active, or performing its intended operation in relation to another entity or context.
-
C.
hasOperationalComponent
Indicates that an entity includes, uses, or depends on another entity as a functional or operational part of its overall system or process.
-
D.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
E.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f1dee08190bfe78564c65f01ad |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.