Triple
T32097153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Ring |
E819748
|
entity |
| Predicate | originalBearer |
P164793
|
FINISHED |
| Object | Círdan |
—
|
NE NERFINISHED |
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: Círdan | Statement: [Red Ring, originalBearer, Círdan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBearer Context triple: [Red Ring, originalBearer, Círdan]
-
A.
formerBearer
Indicates that an entity previously held or carried something (such as a title, role, or object) but no longer does so.
-
B.
firstBearer
Indicates that the subject is the earliest or original entity to hold, possess, or carry the specified role, title, attribute, or item.
-
C.
hasOriginalBearer
chosen
Indicates that something was initially possessed, held, or borne by a particular entity before any transfer, change, or reassignment occurred.
-
D.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
E.
eraOfBearer
Indicates that a time period or era is associated with, or characterizes, the bearer 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a016777257081908841c5522dfa76e6 |
completed | May 11, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_6a0164e49bec8190af3c8626be9677a9 |
completed | May 11, 2026, 5:11 a.m. |
Created at: May 1, 2026, 12:26 a.m.