Triple
T36064390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansi Ganga |
E1043178
|
entity |
| Predicate | consideredNonDifferentFrom |
P142622
|
FINISHED |
| Object | Ganga River |
—
|
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: Ganga River | Statement: [Mansi Ganga, consideredNonDifferentFrom, Ganga River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredNonDifferentFrom Context triple: [Mansi Ganga, consideredNonDifferentFrom, Ganga River]
-
A.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
B.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
C.
usedToBeSameAs
Indicates that two entities were identical or represented the same thing at some point in the past, but no longer do.
-
D.
isDynamicallyDistinctFrom
Indicates that two entities differ in their behavior, state changes, or evolution over time, even if they may appear similar in static properties.
-
E.
isNotKnownToBeEquivalentTo
chosen
Indicates that there is no established or recognized evidence that one entity is equivalent to another.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.