Triple
T18399238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyasa |
E449946
|
entity |
| Predicate | birthPlaceDescription |
P1
|
FINISHED |
| Object | born on an island in the Yamuna or Ganga (traditional belief) |
—
|
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: born on an island in the Yamuna or Ganga (traditional belief) | Statement: [Vyasa, birthPlaceDescription, born on an island in the Yamuna or Ganga (traditional belief)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthPlaceDescription Context triple: [Vyasa, birthPlaceDescription, born on an island in the Yamuna or Ganga (traditional belief)]
-
A.
placeOfBirth
chosen
Indicates the location where a person or other entity was born.
-
B.
creatorPlaceOfBirth
Indicates that the place specified is the location where the creator of an entity was born.
-
C.
placeOfUpbringing
Indicates the location where an individual was raised or spent most of their formative years.
-
D.
fatherPlaceOfBirth
Indicates the location where a person's father was born.
-
E.
namedAfterBirthPlace
Indicates that an entity is given a name derived from or based on the place where it was born.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518499b1481909c5de786c48faeba |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.