Triple
T21058495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teles |
E518785
|
entity |
| Predicate | hasPrimarySourceStatus |
P68515
|
FINISHED |
| Object | poorly attested |
—
|
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: poorly attested | Statement: [Teles, hasPrimarySourceStatus, poorly attested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySourceStatus Context triple: [Teles, hasPrimarySourceStatus, poorly attested]
-
A.
hasPrimarySourceType
Indicates that something is associated with a main or original type of source from which information or evidence is directly obtained.
-
B.
hasSecondarySource
Indicates that an entity is supported, documented, or referenced by a secondary source rather than by a primary or original source.
-
C.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
D.
sourceStatus
chosen
Indicates the current state or condition of a given source within a process, system, or workflow.
-
E.
hasSourceOfData
Indicates that one entity serves as the origin or provider of the data used or referenced by 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_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. |
Created at: April 16, 2026, 2:37 p.m.