Triple
T35086376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris, Banks of the Seine |
E1012586
|
entity |
| Predicate | mainMunicipalAuthority |
P91674
|
FINISHED |
| Object | City of Paris |
—
|
NE NERFINISHED |
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: City of Paris | Statement: [Paris, Banks of the Seine, mainMunicipalAuthority, City of Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMunicipalAuthority Context triple: [Paris, Banks of the Seine, mainMunicipalAuthority, City of Paris]
-
A.
servesAsMunicipalAuthorityFor
Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
-
B.
mainMunicipality
chosen
Indicates that one municipality serves as the primary or central administrative municipality associated with another entity or area.
-
C.
cityAuthority
Indicates that an entity holds official governing or administrative authority over a city.
-
D.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
E.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.