Triple
T31068644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weyland Corporation |
E791751
|
entity |
| Predicate | operatesSpacecraft |
P13424
|
FINISHED |
| Object | USCSS Prometheus |
E197260
|
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: USCSS Prometheus | Statement: [Weyland Corporation, operatesSpacecraft, USCSS Prometheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesSpacecraft Context triple: [Weyland Corporation, operatesSpacecraft, USCSS Prometheus]
-
A.
usesSpacecraft
chosen
Indicates that one entity operates, employs, or relies on a spacecraft to perform an action or fulfill a function in relation to another entity or context.
-
B.
spacecraftCommanded
Indicates that one entity served as the commanding authority or leader of a particular spacecraft.
-
C.
operatesRocket
Indicates that one entity controls or pilots the operation of a rocket belonging to or used by another entity.
-
D.
hostSpacecraft
Indicates that one entity serves as the platform or carrier on which another spacecraft is mounted, accommodated, or operated.
-
E.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
- F. None of above.
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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292b1c1e24819081d4190644d23876 |
completed | June 10, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: April 29, 2026, 9:01 p.m.