Triple
T28974562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhûn |
E734372
|
entity |
| Predicate | hasUncertainGeography |
P133397
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rhûn, hasUncertainGeography, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncertainGeography Context triple: [Rhûn, hasUncertainGeography, true]
-
A.
geographicalCertainty
Indicates the degree of confidence or precision with which a location or geographic reference is known, specified, or assigned in the relationship.
-
B.
hasUncertainOrigin
Indicates that the origin or source of an entity, event, or information is unknown, unclear, or not reliably established.
-
C.
hasUncertainHistoricBasis
Indicates that the historical foundation or authenticity of the related fact, event, or relationship is doubtful, disputed, or not firmly established.
-
D.
uncertainModernLocation
chosen
Indicates that the present-day geographic location associated with an entity is not known with certainty or cannot be reliably determined.
-
E.
hasUncertainNature
Indicates that the nature, status, or characteristics of the relationship or situation are not clearly defined, known, or determined.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 9:07 a.m.