Triple
T25959493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vengi region |
E645496
|
entity |
| Predicate | modernEquivalentIncludes |
P21626
|
FINISHED |
| Object | Godavari districts of Andhra Pradesh |
—
|
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: Godavari districts of Andhra Pradesh | Statement: [Vengi region, modernEquivalentIncludes, Godavari districts of Andhra Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernEquivalentIncludes Context triple: [Vengi region, modernEquivalentIncludes, Godavari districts of Andhra Pradesh]
-
A.
modernEquivalent
chosen
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
-
B.
modernUse
Indicates how something is currently used or applied in modern times.
-
C.
modernExample
Indicates that something serves as a contemporary or current-day instance or illustration of something else.
-
D.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
E.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 22, 2026, 8:47 a.m.