Triple
T35137910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nirn |
E1014622
|
entity |
| Predicate | hasPlaneRelation |
P194575
|
FINISHED |
| Object | adjacent to Oblivion |
—
|
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: adjacent to Oblivion | Statement: [Nirn, hasPlaneRelation, adjacent to Oblivion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaneRelation Context triple: [Nirn, hasPlaneRelation, adjacent to Oblivion]
-
A.
associatedPlane
Indicates a relationship where one entity is linked or connected to a specific plane, typically as the plane it uses, refers to, or is defined with respect to.
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
hasShapeRelation
Indicates that one entity is related to another through a specific geometric or spatial shape relationship (such as similarity, congruence, or containment of shape).
-
D.
hasRelatedPolygon
Indicates that one entity is associated with another entity that is represented or defined as a polygon.
-
E.
hasLandscapeRelation
Indicates a spatial or visual relationship between entities within a landscape, such as positioning, adjacency, or contextual association in the environment.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: May 3, 2026, 4:02 p.m.