Triple
T35012090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmeris |
E1009959
|
entity |
| Predicate | hasInUniverseRegion |
P99968
|
FINISHED |
| Object | Summerset Isles |
—
|
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: Summerset Isles | Statement: [Altmeris, hasInUniverseRegion, Summerset Isles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseRegion Context triple: [Altmeris, hasInUniverseRegion, Summerset Isles]
-
A.
inUniverseRegion
chosen
Indicates that an entity is located within or belongs to a specific universe-defined region or area.
-
B.
hasInUniverseLocationRelation
Indicates a relationship where an entity is associated with, or situated at, a specific location within a fictional or defined universe or setting.
-
C.
hasInUniverseCondition
Indicates that an entity is associated with a condition or rule that applies specifically within a particular fictional or defined universe.
-
D.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 3, 2026, 4:01 p.m.