Triple
T21134996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HL-20 Personnel Launch System |
E520793
|
entity |
| Predicate | crewSeating |
P2608
|
FINISHED |
| Object | reclined seats for launch and reentry |
—
|
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: reclined seats for launch and reentry | Statement: [HL-20 Personnel Launch System, crewSeating, reclined seats for launch and reentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewSeating Context triple: [HL-20 Personnel Launch System, crewSeating, reclined seats for launch and reentry]
-
A.
PPSeats
Indicates that an entity provides or contains seats, typically specifying the seating capacity or arrangement associated with it.
-
B.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
C.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
D.
hasSeating
chosen
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
E.
crewAndPassengersCount
Indicates the total number of people on a vehicle or vessel, combining both crew members and passengers.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723592fd48190ba5977a1b229d51e |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.