Triple
T6865351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prisoner of War Medal |
E158386
|
entity |
| Predicate | statusRequired |
P43873
|
FINISHED |
| Object | prisoner of war |
—
|
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: prisoner of war | Statement: [Prisoner of War Medal, statusRequired, prisoner of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusRequired Context triple: [Prisoner of War Medal, statusRequired, prisoner of war]
-
A.
requiresStatus
chosen
Indicates that one entity can only proceed, be valid, or be applied if another entity has a specified status or condition.
-
B.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
C.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
D.
approvalRequirement
Indicates that one entity must grant permission or authorization before another entity’s action, decision, or state change can proceed.
-
E.
registrationRequirement
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.