Triple
T12917097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise-B |
E309012
|
entity |
| Predicate | missionTypeOnMaidenVoyage |
P107003
|
FINISHED |
| Object | publicity cruise |
—
|
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: publicity cruise | Statement: [USS Enterprise-B, missionTypeOnMaidenVoyage, publicity cruise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionTypeOnMaidenVoyage Context triple: [USS Enterprise-B, missionTypeOnMaidenVoyage, publicity cruise]
-
A.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
B.
missionTypeSupport
Indicates that one entity provides support or assistance to another within the context of a specific mission or operation.
-
C.
missionTypeEstablished
Indicates that a specific type or category of mission has been formally defined and put into effect.
-
D.
missionID
Indicates a unique identifier that associates an entity with a specific mission or operation.
-
E.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a1e8088190af697629baecf59f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.