Triple
T37471905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Other Side |
E931173
|
entity |
| Predicate | primaryZone |
P55012
|
FINISHED |
| Object | Ardenweald |
E273804
|
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: Ardenweald | Statement: [De Other Side, primaryZone, Ardenweald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryZone Context triple: [De Other Side, primaryZone, Ardenweald]
-
A.
primaryRealm
Indicates that one entity is the main or principal realm, domain, or sphere of activity associated with another entity.
-
B.
primaryZoneForCapital
Indicates that a particular geographic or administrative zone is the main zone associated with a given capital.
-
C.
primaryFor
chosen
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
D.
primaryDomain
Indicates that one domain is the main or most important domain associated with an entity, as opposed to any secondary or alternate domains.
-
E.
primaryStation
Indicates that one station is designated as the main or principal station associated with another entity or within a given context.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41852701608190b52cab3f46b40600 |
completed | June 28, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.