Triple
T37487480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iacon |
E931569
|
entity |
| Predicate | statusDuringGreatWar |
P201123
|
FINISHED |
| Object | primary Autobot bastion |
—
|
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: primary Autobot bastion | Statement: [Iacon, statusDuringGreatWar, primary Autobot bastion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringGreatWar Context triple: [Iacon, statusDuringGreatWar, primary Autobot bastion]
-
A.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
B.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
C.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
-
D.
duringWorldWar
Indicates that one entity’s action, state, or relationship occurred within the temporal span of World War II.
-
E.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ffc894cef481908dae1d9cdc7d9d1f |
completed | May 9, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.