Triple
T230961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Geneva |
E4408
|
entity |
| Predicate | hasInternationalRole |
P5590
|
FINISHED |
| Object | major diplomatic hub |
—
|
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: major diplomatic hub | Statement: [canton of Geneva, hasInternationalRole, major diplomatic hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalRole Context triple: [canton of Geneva, hasInternationalRole, major diplomatic hub]
-
A.
hasInternationalOrganizationRole
Indicates that an entity holds or has held a specific role, position, or function within an international organization.
-
B.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
C.
keyInternationalActor
chosen
Indicates that an entity plays a significant and influential role in international affairs or global interactions.
-
D.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
E.
typeOfDiplomaticRole
Indicates the specific kind or category of diplomatic position or function that an entity holds in relation to another.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.