Triple
T12917111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise-B |
E309012
|
entity |
| Predicate | rescueMissionTarget |
P60884
|
FINISHED |
| Object | El-Aurian refugee ships |
—
|
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: El-Aurian refugee ships | Statement: [USS Enterprise-B, rescueMissionTarget, El-Aurian refugee ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescueMissionTarget Context triple: [USS Enterprise-B, rescueMissionTarget, El-Aurian refugee ships]
-
A.
isTargetOfMission
chosen
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
B.
insurgentObjective
Indicates that an insurgent group or actor has a specific strategic goal, target, or desired outcome they are attempting to achieve.
-
C.
targetLocation
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
D.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
- 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_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. |
Created at: April 9, 2026, 5:41 p.m.