Triple
T13945993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frogfoot |
E335385
|
entity |
| Predicate | aircraftNamedCrew |
P94498
|
FINISHED |
| Object | 1 (standard attack version) |
—
|
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: 1 (standard attack version) | Statement: [Frogfoot, aircraftNamedCrew, 1 (standard attack version)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftNamedCrew Context triple: [Frogfoot, aircraftNamedCrew, 1 (standard attack version)]
-
A.
hasFlightCrew
Indicates that an entity (such as a flight or aircraft) is associated with one or more people serving as its flight crew.
-
B.
firstCrewedTestFlightCrew
Indicates that the subject is a member of the crew on the first crewed test flight of the referenced vehicle or mission.
-
C.
crewOnboard
chosen
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
D.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
E.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e10f60c81908ee9636e85c070ff |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.