Triple
T32774489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Petersburg |
E838157
|
entity |
| Predicate | hasHeadOfCity |
P123058
|
FINISHED |
| Object | Governor of Saint Petersburg |
—
|
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: Governor of Saint Petersburg | Statement: [Saint Petersburg, hasHeadOfCity, Governor of Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadOfCity Context triple: [Saint Petersburg, hasHeadOfCity, Governor of Saint Petersburg]
-
A.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
B.
hasHeadOfLocalGovernment
chosen
Indicates that an administrative area is associated with the person who serves as its chief local government official.
-
C.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
D.
hasCityManager
Indicates that an entity has a specific individual who serves in the role of city manager for it.
-
E.
hasMayor
Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:13 a.m.