Triple
T25693365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrinathji |
E644254
|
entity |
| Predicate | associatedPoets |
P137138
|
FINISHED |
| Object | Ashtachap poets |
—
|
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: Ashtachap poets | Statement: [Shrinathji, associatedPoets, Ashtachap poets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPoets Context triple: [Shrinathji, associatedPoets, Ashtachap poets]
-
A.
poetAssociated
Indicates a relationship where a poet is connected or linked to another entity, such as a work, place, movement, or person, through relevance, collaboration, influence, or affiliation.
-
B.
associatedWithPoem
Indicates a relationship in which an entity is connected or linked to a particular poem, such as by authorship, subject, reference, or contextual association.
-
C.
includesPoetsFrom
chosen
Indicates that one entity contains, features, or is composed of poets originating from another entity.
-
D.
favoritePoet
Indicates that one entity is the poet whom another entity prefers above all other poets.
-
E.
featuredPoet
Indicates that a person is highlighted or showcased as a poet in a special or prominent context.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 21, 2026, 8:31 p.m.