Triple
T36654737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Ring of Power |
E904957
|
entity |
| Predicate | unique |
P163991
|
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: [the Ring of Power, unique, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unique Context triple: [the Ring of Power, unique, true]
-
A.
uniqueAspect
chosen
Indicates that the subject possesses a distinctive feature or characteristic that sets it apart from others.
-
B.
exclusive
Indicates that the relationship or action applies only to a specific entity or set of entities, excluding all others from sharing that same status or participation.
-
C.
uniqueClaim
Indicates that a claim is distinct and not duplicated or shared with any other claim in the given context.
-
D.
uniqueUpTo
Indicates that one entity is determined uniquely by another, except for differences within a specified equivalence or tolerance (i.e., unique modulo that relation).
-
E.
solitary
Indicates that an entity exists, acts, or is characterized in isolation, without the presence or involvement of others.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.