Triple
T12203062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahad 1 |
E290763
|
entity |
| Predicate | awardsConferred |
P21360
|
FINISHED |
| Object | officer rank insignia upon completion |
—
|
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: officer rank insignia upon completion | Statement: [Bahad 1, awardsConferred, officer rank insignia upon completion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardsConferred Context triple: [Bahad 1, awardsConferred, officer rank insignia upon completion]
-
A.
awardConferred
chosen
Indicates that an award or honor has been formally granted by one entity to another.
-
B.
recipientOfAward
Indicates that an entity has received or been granted a particular award.
-
C.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
D.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
-
E.
awardReceivedWith
Indicates that an entity received a specific award, optionally together with additional contextual details such as the work, role, or circumstances associated with that award.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.