Triple
T31744379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-bomber force |
E810228
|
entity |
| Predicate | VulcanRetirement |
P2089
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [V-bomber force, VulcanRetirement, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VulcanRetirement Context triple: [V-bomber force, VulcanRetirement, 1980s]
-
A.
VulcanRole
Indicates a role or function that an entity holds within the context of Vulcan (e.g., Vulcan-related positions, duties, or capacities).
-
B.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
-
C.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
-
D.
retired
chosen
Indicates that an entity has permanently stopped working in their former occupation or role, typically after reaching a certain age or service duration.
-
E.
plannedRetirement
Indicates that an entity has scheduled or intends to end its active role or service at a specified future time.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:26 p.m.