Triple
T36546378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelion (via channels after the Breaking of Thargelion) |
E901151
|
entity |
| Predicate | associatedRegionBefore |
P27947
|
FINISHED |
| Object | Thargelion |
E397468
|
NE 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: Thargelion | Statement: [Gelion (via channels after the Breaking of Thargelion), associatedRegionBefore, Thargelion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRegionBefore Context triple: [Gelion (via channels after the Breaking of Thargelion), associatedRegionBefore, Thargelion]
-
A.
associatedRegionFeature
Indicates that something is linked or connected to a particular geographic or regional feature.
-
B.
formerServesRegion
chosen
Indicates that an entity previously served, represented, or had official responsibility for a given region, but no longer does so.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
E.
associatedRegions
Indicates that there is a relevant connection or linkage between an entity and one or more geographic or administrative regions.
- F. None of above.
Provenance (4 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39e6e9d0f4819086a1633b89222140 |
completed | June 23, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.