Triple
T20386093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narada |
E497958
|
entity |
| Predicate | target |
P860
|
FINISHED |
| Object | planet Vulcan |
—
|
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: planet Vulcan | Statement: [Narada, target, planet Vulcan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: planet Vulcan Context triple: [Narada, target, planet Vulcan]
-
A.
planet Vulcan
Planet Vulcan is the fictional homeworld of Spock and the Vulcan species in the Star Trek universe, known for its harsh desert environment and culture of strict logic and emotional control.
-
B.
Vulcun
Vulcun was a North American professional League of Legends esports team that competed in the early seasons of the League Championship Series (LCS).
-
C.
Vulcan
chosen
Vulcan is a fictional desert planet in the Star Trek universe, known as the logical and emotion-suppressing home of the Vulcan species, including Spock.
-
D.
Vulcan
Vulcan is a small town in southern Alberta, Canada, best known for embracing a Star Trek theme that attracts science fiction fans and tourists.
-
E.
Vulcan
Vulcan is the Roman god of fire, metalworking, and the forge, often depicted as a blacksmith crafting weapons and armor for the gods.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790bcef481909453d19c846ab420 |
completed | April 20, 2026, 7:05 p.m. |
Created at: April 16, 2026, 11:28 a.m.