Triple
T33310857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USCSS Nostromo |
E852871
|
entity |
| Predicate | hasLandingModule |
P198345
|
FINISHED |
| Object | separate refinery and cargo platform |
—
|
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: separate refinery and cargo platform | Statement: [USCSS Nostromo, hasLandingModule, separate refinery and cargo platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandingModule Context triple: [USCSS Nostromo, hasLandingModule, separate refinery and cargo platform]
-
A.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
B.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
C.
hasIslandLanding
Indicates that an entity includes or provides a designated landing area or facility located on an island.
-
D.
hasLandingCharacteristics
Indicates that an entity possesses specific attributes or features related to how it lands or is capable of landing.
-
E.
hasLandingFacilities
Indicates that a location or structure is equipped with facilities that allow aircraft or other vehicles to land there.
- F. None of above. chosen
Provenance (4 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
| PDg | Predicate description generation | batch_69fedec5e1708190a0b13be7533d55d8 |
completed | May 9, 2026, 7:14 a.m. |
Created at: May 1, 2026, 1:33 a.m.