Triple
T37250693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ise |
E923977
|
entity |
| Predicate | airRaid |
P187342
|
FINISHED |
| Object | Kure air raids 1945 |
—
|
NE NERFINISHED |
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: Kure air raids 1945 | Statement: [Ise, airRaid, Kure air raids 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airRaid Context triple: [Ise, airRaid, Kure air raids 1945]
-
A.
airCommander
Indicates that an entity serves as the commanding officer or leader of air forces or air operations for another entity.
-
B.
airGroupCommanderAttacker
Indicates that the subject serves as the commanding officer of an air group that is carrying out an attack.
-
C.
airArm
Indicates that an entity is equipped with or operates an air-based military force or aviation arm.
-
D.
aerialUnit
Indicates that the related entity functions as or is classified as an aerial unit, typically operating or acting in the air rather than on the ground or sea.
-
E.
airWingComplement
Indicates that one entity serves as the aircraft or air unit complement assigned to another entity, typically a ship or larger military formation.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb41333b548190912cb238ffc271c9 |
completed | May 6, 2026, 1:25 p.m. |
Created at: May 3, 2026, 4:15 p.m.