Triple
T25947018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ком–Емине |
E653866
|
entity |
| Predicate | endAt |
P159591
|
FINISHED |
| Object | Black Sea |
—
|
NE NERFINISHED |
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: Black Sea | Statement: [Ком–Емине, endAt, Black Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endAt Context triple: [Ком–Емине, endAt, Black Sea]
-
A.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
nameOfEndAt
Indicates that something has the specified name at the point or time when it ends.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
- F. None of above. chosen
Provenance (4 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_69f60466a32c8190a73b55901951a9e1 |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:43 a.m.