Triple
T4118261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratolaunch carrier aircraft |
E90345
|
entity |
| Predicate | crewPlacement |
P42883
|
FINISHED |
| Object | right fuselage |
—
|
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: right fuselage | Statement: [Stratolaunch carrier aircraft, crewPlacement, right fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewPlacement Context triple: [Stratolaunch carrier aircraft, crewPlacement, right fuselage]
-
A.
crewLocation
Indicates that a crew is located at, assigned to, or present in a specific place or environment.
-
B.
placementIn
chosen
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
C.
qualificationSpotAllocation
Indicates the assignment of available qualification spots or slots to entities based on predefined criteria or results.
-
D.
divisionPlacement
Indicates that one entity is assigned or positioned within a particular division or subgroup of another entity.
-
E.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.