Triple
T35510695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galaxy News Radio |
E1026277
|
entity |
| Predicate | primaryQuestHubFor |
P2958
|
FINISHED |
| Object | Lone Wanderer |
E1009932
|
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: Lone Wanderer | Statement: [Galaxy News Radio, primaryQuestHubFor, Lone Wanderer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryQuestHubFor Context triple: [Galaxy News Radio, primaryQuestHubFor, Lone Wanderer]
-
A.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
B.
primaryHubFor
chosen
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
C.
introducedQuestHub
Indicates that an entity has presented or made a quest hub available to another entity or group.
-
D.
questHubNPC
Indicates that an NPC serves as a central provider or coordinator of quests for players.
-
E.
hasQuestHubIn
Indicates that a quest hub is located within or associated with a particular place or region.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389bffe5d081909f4917c712268c2c |
completed | June 22, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.