Triple
T34863421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmer |
E1004943
|
entity |
| Predicate | viewOfOtherMer |
P180519
|
FINISHED |
| Object | see themselves as closest to original Aldmer |
—
|
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: see themselves as closest to original Aldmer | Statement: [Altmer, viewOfOtherMer, see themselves as closest to original Aldmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOfOtherMer Context triple: [Altmer, viewOfOtherMer, see themselves as closest to original Aldmer]
-
A.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
B.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
C.
viewOnOtherHumans
chosen
Indicates how one individual perceives, judges, or forms attitudes toward other human beings.
-
D.
viewedBy
Indicates that something has been seen, observed, or watched by a particular entity.
-
E.
viewsOtherPathsAs
Indicates that one entity perceives, interprets, or regards alternative paths, routes, or courses of action in a particular way relative to another entity.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4 p.m.