Triple
T29082605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quad Blasters |
E734018
|
entity |
| Predicate | originUniverseLocation |
P39506
|
FINISHED |
| Object | outer space |
—
|
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: outer space | Statement: [Quad Blasters, originUniverseLocation, outer space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originUniverseLocation Context triple: [Quad Blasters, originUniverseLocation, outer space]
-
A.
inUniverseOrigin
chosen
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
-
B.
inUniverseBirthplace
Indicates that an entity’s birthplace is located within a specified fictional or defined universe.
-
C.
builtLocationInUniverse
Indicates that a construction or structure was created or established at a specific location within a particular universe or cosmic setting.
-
D.
homeTownInUniverse
Indicates that a location is the character’s hometown within a specified fictional or defined universe.
-
E.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: April 28, 2026, 10:56 a.m.