Triple
T33687963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honor Guard |
E863092
|
entity |
| Predicate | dutyRequirement |
P109992
|
FINISHED |
| Object | strict uniform standards |
—
|
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: strict uniform standards | Statement: [Honor Guard, dutyRequirement, strict uniform standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dutyRequirement Context triple: [Honor Guard, dutyRequirement, strict uniform standards]
-
A.
expectedDuty
chosen
Indicates that one entity is obligated or anticipated to perform a particular duty or responsibility toward another entity or within a given context.
-
B.
performsDuty
Indicates that one entity carries out or fulfills a responsibility, task, or obligation on behalf of or in relation to another entity.
-
C.
maintenanceRequirement
Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
-
D.
dutyRecognized
Indicates that an obligation or responsibility has been acknowledged or accepted by the relevant party.
-
E.
statutoryDuty
Indicates that an entity is legally obligated by statute to perform, refrain from, or ensure a specific action or condition.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa65e4008190ace046bbbd856793 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.