Triple
T33564714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pictet |
E859724
|
entity |
| Predicate | isLinkedToCity |
P25162
|
FINISHED |
| Object | Geneva |
—
|
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: Geneva | Statement: [Pictet, isLinkedToCity, Geneva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinkedToCity Context triple: [Pictet, isLinkedToCity, Geneva]
-
A.
hasAssociatedCity
chosen
Indicates that one entity is linked or related to a specific city, typically as its location, base, or primary area of association.
-
B.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
-
C.
isCityOf
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
-
D.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
E.
refersToCityOn
Indicates that one entity makes reference to, or is specifically about, a particular city located on a given date or temporal context.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f715bc3c8190abc7015a6d06c3a6 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.