Triple
T33095202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farmer |
E846889
|
entity |
| Predicate | aircraftTypeOfDesignatedAircraft |
P1524
|
FINISHED |
| Object | jet aircraft |
—
|
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: jet aircraft | Statement: [Farmer, aircraftTypeOfDesignatedAircraft, jet aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeOfDesignatedAircraft Context triple: [Farmer, aircraftTypeOfDesignatedAircraft, jet aircraft]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
aircraftRoleOfDesignatedAircraft
Indicates that an aircraft has the specified operational role or function as a designated aircraft within a particular context or mission.
-
C.
iataAircraftTypeCode
Indicates the standardized IATA code that specifies the aircraft type used in a flight or aviation context.
-
D.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
E.
aircraftTypeManaged
Indicates that one entity is responsible for managing or overseeing a particular type or category of aircraft.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:26 a.m.