Triple
T17598217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallente Federation |
E428627
|
entity |
| Predicate | playableRaceGroup |
P51003
|
FINISHED |
| Object | Gallente characters |
—
|
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: Gallente characters | Statement: [Gallente Federation, playableRaceGroup, Gallente characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableRaceGroup Context triple: [Gallente Federation, playableRaceGroup, Gallente characters]
-
A.
playableRace
Indicates that an entity is a race or species that players are allowed to choose and control in a game or interactive system.
-
B.
relatedRace
chosen
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
C.
canBeOfAnyRace
Indicates that the subject is not restricted to a specific race and may belong to any racial group.
-
D.
raceOfBearers
Indicates the racial or ethnic group to which the bearers (individuals or entities) belong.
-
E.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ecfb108190a9e7a5b380f8ab93 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.