Triple
T31381889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 155th Air Refueling Wing |
E800481
|
entity |
| Predicate | activeAsAirRefuelingWingSince |
P180165
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [155th Air Refueling Wing, activeAsAirRefuelingWingSince, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsAirRefuelingWingSince Context triple: [155th Air Refueling Wing, activeAsAirRefuelingWingSince, 1994]
-
A.
usedAsPresidentialAircraftUntil
Indicates that an aircraft served in the official role of presidential transport up to a specified end date.
-
B.
aircraftEnteredServiceWith
Indicates that an aircraft began its operational service or was officially introduced into use with a specified operator, organization, or context.
-
C.
usedAerialRefueling
Indicates that one entity received fuel in flight from another entity via aerial refueling.
-
D.
usedByAirForce
Indicates that something is employed, operated, or otherwise utilized by an air force.
-
E.
enteredUSAFServiceAs
Indicates that an individual began active service in the United States Air Force in a specified role, rank, or capacity.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 29, 2026, 9:19 p.m.