Triple
T1107242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peacetime Distinguished Service Award |
E25512
|
entity |
| Predicate | mayBePresentedBy |
P83
|
FINISHED |
| Object | head of organization |
—
|
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: head of organization | Statement: [Peacetime Distinguished Service Award, mayBePresentedBy, head of organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBePresentedBy Context triple: [Peacetime Distinguished Service Award, mayBePresentedBy, head of organization]
-
A.
presentedBy
chosen
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
B.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
C.
mayServeOn
Indicates that one entity is permitted or eligible to serve on another entity, such as a group, body, or committee.
-
D.
requiresPresence
Indicates that one entity’s existence, operation, or validity depends on another entity being present or available.
-
E.
presentedFor
Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e47e4881908928900df72781f0 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.