Triple
T2825387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakshin Ganga |
E54906
|
entity |
| Predicate | analogousRole |
P21749
|
FINISHED |
| Object | southern counterpart of the Ganges |
—
|
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: southern counterpart of the Ganges | Statement: [Dakshin Ganga, analogousRole, southern counterpart of the Ganges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analogousRole Context triple: [Dakshin Ganga, analogousRole, southern counterpart of the Ganges]
-
A.
roleSimilarTo
chosen
Indicates that two entities have roles or functions that are alike or closely comparable in nature or responsibility.
-
B.
comparativeRole
Indicates a relationship where one entity’s role is compared to another’s in terms of level, importance, or function.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
E.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.