Triple
T29526668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-POD |
E749086
|
entity |
| Predicate | typicalMountingLocation |
P29518
|
FINISHED |
| Object | exterior of a launch vehicle upper stage |
—
|
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: exterior of a launch vehicle upper stage | Statement: [P-POD, typicalMountingLocation, exterior of a launch vehicle upper stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMountingLocation Context triple: [P-POD, typicalMountingLocation, exterior of a launch vehicle upper stage]
-
A.
mountingLocation
chosen
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
B.
typicalLocationOnProduct
Indicates the usual physical place or area on a product where something (e.g., a feature, label, or component) is commonly found.
-
C.
typicalControlLocation
Indicates the usual or standard physical location from which control or operation of something is exercised.
-
D.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
E.
typicalStorePlacement
Indicates the usual or standard physical location where an item is placed or displayed within a store.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a01d077dcec8190b05b24b5de313b15 |
completed | May 11, 2026, 12:50 p.m. |
| PD | Predicate disambiguation | batch_6a01cea0e37881909cb6888518c6d12f |
completed | May 11, 2026, 12:42 p.m. |
Created at: April 28, 2026, 4:47 p.m.