Triple
T19575854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarabhanga |
E489855
|
entity |
| Predicate | locus |
P47308
|
FINISHED |
| Object | hermitage in the Dandaka forest |
—
|
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: hermitage in the Dandaka forest | Statement: [Sarabhanga, locus, hermitage in the Dandaka forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locus Context triple: [Sarabhanga, locus, hermitage in the Dandaka forest]
-
A.
locusDescription
Indicates how the spatial position or location of an entity is described or characterized.
-
B.
subjectLocation
chosen
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
C.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
-
E.
labelLocation
Indicates that a label or identifier is associated with a specific spatial or geographic location.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64024c5b08190bbff6df633857874 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.