Triple
T21058490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teles |
E518785
|
entity |
| Predicate | hasNotabilityLevel |
P142673
|
FINISHED |
| Object | obscure |
—
|
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: obscure | Statement: [Teles, hasNotabilityLevel, obscure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotabilityLevel Context triple: [Teles, hasNotabilityLevel, obscure]
-
A.
hasNotabilityCategory
Indicates that an entity is associated with a particular category that characterizes its type or area of notability.
-
B.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
-
C.
lacksNotabilityAs
Indicates that one entity is considered insufficiently notable or significant to be associated with or classified as the other entity.
-
D.
hasNotabilitySource
Indicates that there exists an external, recognized source that attests to or supports the notability or significance of the subject entity.
-
E.
hasNotabilityOrigin
Indicates that an entity’s notability or prominence arises from, or is primarily associated with, a specified origin (such as a place, context, or source).
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd8236b481908eebfaeeb2aa63e6 |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:37 p.m.