Triple
T9009348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aichi B7A |
E215427
|
entity |
| Predicate | enteredServiceLateInWar |
P85704
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aichi B7A, enteredServiceLateInWar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceLateInWar Context triple: [Aichi B7A, enteredServiceLateInWar, true]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
roleChangeLaterWar
Indicates that an entity’s role or position changes at a later stage within the context of a war or armed conflict.
-
C.
musteredIntoService
Indicates that an entity has been formally enrolled or assembled into active duty or official service under an authority.
-
D.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
E.
enteredCombatInEurope
Indicates that an entity became actively involved in military combat operations within the geographical region of Europe.
- F. None of above. chosen
Provenance (4 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69c00ae8819090786385a72e8baf |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:06 p.m.