Triple
T10409364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putilovo |
E245345
|
entity |
| Predicate | regionDuringEvent |
P93971
|
FINISHED |
| Object | vicinity of Moscow |
—
|
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: vicinity of Moscow | Statement: [Putilovo, regionDuringEvent, vicinity of Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDuringEvent Context triple: [Putilovo, regionDuringEvent, vicinity of Moscow]
-
A.
regionDuringBR
Indicates that a region exists or is valid specifically during a defined base or reference time interval (BR).
-
B.
inForceDuringEvent
Indicates that a rule, condition, or state is actively valid and applicable throughout the duration of a specified event.
-
C.
operatorDuringEvent
Indicates that an operator is actively performing their role or function throughout the duration of a specified event.
-
D.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
E.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9faa97c819092cadedadabe26bf |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:09 p.m.