Triple
T37315568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dome of Stars |
E926322
|
entity |
| Predicate | realmRole |
P187728
|
FINISHED |
| Object | early capital seat of Gondor |
—
|
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: early capital seat of Gondor | Statement: [Dome of Stars, realmRole, early capital seat of Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmRole Context triple: [Dome of Stars, realmRole, early capital seat of Gondor]
-
A.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
B.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
C.
registryRole
Indicates the specific function or capacity an entity holds within a registry, such as how it participates in or is responsible for registry-related activities.
-
D.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
E.
tenantRole
Indicates that an entity holds the role or capacity of a tenant in relation to another entity (such as a property or landlord).
- F. None of above. chosen
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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:16 p.m.