Triple
T3598014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lima Shatterdome |
E76186
|
entity |
| Predicate | roleInUniverse |
P48208
|
FINISHED |
| Object | major PPDC base |
—
|
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: major PPDC base | Statement: [Lima Shatterdome, roleInUniverse, major PPDC base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUniverse Context triple: [Lima Shatterdome, roleInUniverse, major PPDC base]
-
A.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
fictionalUniverseRole
chosen
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
-
D.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
E.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc19c71608190a87c98214321214c |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.