Triple
T38311893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romulan–Klingon conflicts |
E1033710
|
entity |
| Predicate | hasParticipantSpecies |
P10920
|
FINISHED |
| Object | Romulans |
—
|
NE NERFINISHED |
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: Romulans | Statement: [Romulan–Klingon conflicts, hasParticipantSpecies, Romulans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticipantSpecies Context triple: [Romulan–Klingon conflicts, hasParticipantSpecies, Romulans]
-
A.
includesSpecies
chosen
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
B.
hasMemberOfSpecies
Indicates that an entity includes, contains, or is associated with one or more individuals belonging to a specified species.
-
C.
hasCompanionSpecies
Indicates that one entity is accompanied by, or exists in association with, another entity of a different species.
-
D.
appearsWithSpecies
Indicates that one entity is observed or recorded together with a particular species in the same context or occurrence.
-
E.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:30 p.m.