Triple
T15609002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simlipal National Park |
E375236
|
entity |
| Predicate | reptileSpecies |
P103109
|
FINISHED |
| Object | mugger crocodile |
—
|
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: mugger crocodile | Statement: [Simlipal National Park, reptileSpecies, mugger crocodile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reptileSpecies Context triple: [Simlipal National Park, reptileSpecies, mugger crocodile]
-
A.
hasReptileSpecies
chosen
Indicates that one entity possesses, contains, or is associated with a reptile species as part of its characteristics or composition.
-
B.
speciesHome
Indicates that a particular location serves as the natural habitat or primary living environment for a given species.
-
C.
enemySpecies
Indicates that two species are in an antagonistic or hostile relationship, typically viewing each other as enemies.
-
D.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
E.
speciesNumber
Indicates the numerical identifier or count associated with a particular species in a given context.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8024948190a6c711f2e5c2aac4 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.