Triple
T5881666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lady with the Dog |
E130761
|
entity |
| Predicate | openingLocation |
P24241
|
FINISHED |
| Object | sea promenade in Yalta |
—
|
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: sea promenade in Yalta | Statement: [The Lady with the Dog, openingLocation, sea promenade in Yalta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingLocation Context triple: [The Lady with the Dog, openingLocation, sea promenade in Yalta]
-
A.
openingShowLocation
Indicates the place where an opening show or premiere event takes place.
-
B.
openingSite
chosen
Indicates the location or site where an opening or access point is created, occurs, or is situated.
-
C.
openedAtCurrentLocation
Indicates that an entity has been opened or initiated at the user’s or system’s current physical or contextual location.
-
D.
launchLocation
Indicates the place or site from which something is launched or set into motion.
-
E.
openingDetail
Indicates the specific manner, context, or characteristics of how an opening (such as a beginning, start, or initial access point) occurs or is carried out between entities.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.