Triple
T25321732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronald Bishop |
E634899
|
entity |
| Predicate | aircraftRoleDesignedFor |
P159104
|
FINISHED |
| Object | pathfinder 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: pathfinder aircraft | Statement: [Ronald Bishop, aircraftRoleDesignedFor, pathfinder aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftRoleDesignedFor Context triple: [Ronald Bishop, aircraftRoleDesignedFor, pathfinder aircraft]
-
A.
aircraftRoleDesignedFor
chosen
Indicates that an aircraft is specifically designed or intended to perform a particular role or function.
-
B.
aircraftRoleDesigned
Indicates that an aircraft was specifically designed to fulfill a particular operational role or function.
-
C.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
-
D.
primaryAircraftRole
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
E.
aircraftRoleSpecialization
Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:28 p.m.