Triple
T25947017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ком–Емине |
E653866
|
entity |
| Predicate | startNear |
P134734
|
FINISHED |
| Object | Serbian border |
—
|
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: Serbian border | Statement: [Ком–Емине, startNear, Serbian border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startNear Context triple: [Ком–Емине, startNear, Serbian border]
-
A.
startedNear
chosen
Indicates that one event or action began close in time or space to another event or action.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
shortestNear
Indicates that one entity is the closest (or among the closest) to another entity compared to other nearby alternatives.
-
D.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
-
E.
occursNear
Indicates that one event or entity takes place or exists in close spatial proximity to another.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 8:43 a.m.