Triple
T38092276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest |
E951145
|
entity |
| Predicate | supportsSuitType |
P207595
|
FINISHED |
| Object | Extravehicular Mobility Unit |
E673856
|
NE 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: Extravehicular Mobility Unit | Statement: [Quest, supportsSuitType, Extravehicular Mobility Unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSuitType Context triple: [Quest, supportsSuitType, Extravehicular Mobility Unit]
-
A.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
C.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
D.
suitFeature
Indicates that a particular feature, characteristic, or attribute is associated with or included in a given suit.
-
E.
suitType
Indicates the specific category or style of suit associated with an entity (e.g., business suit, spacesuit, wetsuit).
- F. None of above. chosen
Provenance (5 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d522b188190be40970580f83946 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:21 p.m.