Triple
T33661653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The River |
E862367
|
entity |
| Predicate | associatedWithAuthorExperienceIn |
P115636
|
FINISHED |
| Object | India |
E1124
|
NE 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: India | Statement: [The River, associatedWithAuthorExperienceIn, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAuthorExperienceIn Context triple: [The River, associatedWithAuthorExperienceIn, India]
-
A.
relatedToAuthorExperience
chosen
Indicates that something has a connection to, is influenced by, or is derived from the author's personal experiences.
-
B.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
C.
associatedWithAuthorRole
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
D.
associatedWithAuthorType
Indicates that one entity has a specified type of association or role in relation to an author.
-
E.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
- F. None of above.
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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c8c00d88190bd9883210d1eec29 |
completed | June 20, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:42 a.m.