Triple
T35058432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keran |
E1011527
|
entity |
| Predicate | nearLineOfControl |
P55118
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Keran, nearLineOfControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearLineOfControl Context triple: [Keran, nearLineOfControl, true]
-
A.
frontLineNear
Indicates that one entity is located close to the primary boundary or front line associated with another entity.
-
B.
nearBorderBetween
chosen
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
-
C.
nearBorderDirection
Indicates that one entity is located close to a border or boundary in a specified directional orientation relative to that border.
-
D.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
E.
approachControl
Indicates that one entity moves closer to another entity in a deliberate or controlled manner.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785d2ed3c8190b3444fbc6e527cb3 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.