Triple
T27752656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhra Pradesh–Karnataka border |
E701250
|
entity |
| Predicate | demarcatedAs |
P156667
|
FINISHED |
| Object | state boundary |
—
|
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: state boundary | Statement: [Andhra Pradesh–Karnataka border, demarcatedAs, state boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demarcatedAs Context triple: [Andhra Pradesh–Karnataka border, demarcatedAs, state boundary]
-
A.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
B.
wasDemarcatedBetween
Indicates that a boundary or dividing line was formally established separating one entity from another.
-
C.
demarcationStatus
Indicates the current state or condition of how clearly and officially a boundary or division between entities is defined or marked.
-
D.
hasDemarcationAuthority
Indicates that an entity possesses the formal power or right to define, set, or modify boundaries or divisions between areas, responsibilities, or categories.
-
E.
areaDefinedAs
chosen
Indicates that one area is formally specified, delimited, or characterized in terms of another area or defining criteria.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63720253c819089ddbecbcbe6401a |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:21 p.m.