Triple
T15316601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sevastopol city embankment |
E366173
|
entity |
| Predicate | typicalActivityTime |
P10350
|
FINISHED |
| Object | daytime |
—
|
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: daytime | Statement: [Sevastopol city embankment, typicalActivityTime, daytime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActivityTime Context triple: [Sevastopol city embankment, typicalActivityTime, daytime]
-
A.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
B.
activityTime
chosen
Indicates the time period during which an activity occurs or is scheduled to take place.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
E.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd1d384819098f38402a8740d91 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.