Triple
T30345368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gun Gale Online |
E771854
|
entity |
| Predicate | inUniverseDeveloper |
P47705
|
FINISHED |
| Object | Zaskar |
—
|
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: Zaskar | Statement: [Gun Gale Online, inUniverseDeveloper, Zaskar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseDeveloper Context triple: [Gun Gale Online, inUniverseDeveloper, Zaskar]
-
A.
inUniverse
chosen
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
-
C.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
-
D.
inUniverseUser
Indicates that a user exists or participates within a specified fictional or conceptual universe.
-
E.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 7:55 p.m.