Triple
T5454651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leningrad City Soviet |
E122448
|
entity |
| Predicate | hadMeetingPlace |
P8904
|
FINISHED |
| Object | Leningrad city council building |
—
|
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: Leningrad city council building | Statement: [Leningrad City Soviet, hadMeetingPlace, Leningrad city council building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMeetingPlace Context triple: [Leningrad City Soviet, hadMeetingPlace, Leningrad city council building]
-
A.
meetingPlaceOf
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
-
B.
firstMeetingPlace
Indicates the location where two or more entities met each other for the very first time.
-
C.
previousMeetingPlace
Indicates the location where two or more entities met on a prior occasion.
-
D.
hasMeetingLocation
chosen
Indicates that an entity (such as a meeting or event) takes place at or is associated with a specific location.
-
E.
mayMeetAt
Indicates that two or more entities are permitted or able to have a meeting or encounter at a specified place or time.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.