Triple
T10978799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amagi |
E259442
|
entity |
| Predicate | statusDuringLateWar |
P19660
|
FINISHED |
| Object | largely inactive due to fuel and aircrew shortages |
—
|
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: largely inactive due to fuel and aircrew shortages | Statement: [Amagi, statusDuringLateWar, largely inactive due to fuel and aircrew shortages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringLateWar Context triple: [Amagi, statusDuringLateWar, largely inactive due to fuel and aircrew shortages]
-
A.
statusDuringWar
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.
statusDuringWorldWarII
chosen
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
D.
statusAfter1942
Indicates the status or condition of an entity as it existed after the year 1942.
-
E.
statusAfter1941
Indicates the condition or state of an entity as it existed after the year 1941.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f7b874819087bf5a858905279b |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.