Triple
T35723560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijayachelys |
E1032546
|
entity |
| Predicate | countryOfOccurrenceOfIncludedSpecies |
P98226
|
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: [Vijayachelys, countryOfOccurrenceOfIncludedSpecies, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfOccurrenceOfIncludedSpecies Context triple: [Vijayachelys, countryOfOccurrenceOfIncludedSpecies, India]
-
A.
inhabitsCountry
chosen
Indicates that an entity lives or resides within the borders of a specified country.
-
B.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
-
C.
biogeographicallyRelatedTo
Indicates that two entities are connected through their biogeographic characteristics, such as shared distribution patterns, regions, or historical biogeographic processes.
-
D.
naturalReservoirOfNotableSpecies
Indicates that a location serves as a natural habitat or reservoir for one or more notable species.
-
E.
countryOfConservationProgram
Indicates the country in which a given conservation program is implemented or officially associated.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01ed1790148190b08c1dba53de4371 |
completed | May 11, 2026, 2:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d1410c88190879bc299b0c0595a |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a01e9c20798819085760b377dc7b3fa |
completed | May 11, 2026, 2:37 p.m. |
Created at: May 3, 2026, 4:05 p.m.