Triple
T27546731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ara Zobayan |
E695382
|
entity |
| Predicate | pilotRatings |
P163279
|
FINISHED |
| Object | instrument helicopter |
—
|
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: instrument helicopter | Statement: [Ara Zobayan, pilotRatings, instrument helicopter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilotRatings Context triple: [Ara Zobayan, pilotRatings, instrument helicopter]
-
A.
pilotRatings
chosen
Indicates that an entity has been assigned or holds specific pilot qualification ratings or certifications.
-
B.
pilotRank
Indicates the rank or level of seniority assigned to a pilot within an aviation or organizational hierarchy.
-
C.
approximatePilots
Indicates that one entity serves as an estimated or provisional pilot for another, rather than an exact or final pilot assignment.
-
D.
isPilotOf
Indicates that one entity serves as the pilot who operates or controls another entity, typically a vehicle or aircraft.
-
E.
notablePilot
Indicates that an entity is a distinguished or noteworthy pilot associated with another entity (such as a vehicle, event, or organization).
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:33 p.m.