Triple
T9848696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navajo Code Talkers |
E239407
|
entity |
| Predicate | codeStatusDuringWar |
P19322
|
FINISHED |
| Object | top secret |
—
|
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: top secret | Statement: [Navajo Code Talkers, codeStatusDuringWar, top secret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeStatusDuringWar Context triple: [Navajo Code Talkers, codeStatusDuringWar, top secret]
-
A.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
B.
stateDuringWar
Indicates that a state or condition exists specifically in the context of, or for the duration of, a war or armed conflict.
-
C.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
D.
supportedDuringWar
Indicates that one entity provided assistance, resources, or backing to another entity specifically during a time of war.
-
E.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb371894c8190971ba497a2801521 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.