Triple
T24023653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azores Summit (2003) |
E594892
|
entity |
| Predicate | hostTerritory |
P107807
|
FINISHED |
| Object | Azores |
—
|
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: Azores | Statement: [Azores Summit (2003), hostTerritory, Azores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostTerritory Context triple: [Azores Summit (2003), hostTerritory, Azores]
-
A.
locationTerritory
chosen
Indicates that one entity is geographically or administratively situated within the territorial bounds or jurisdiction of another entity.
-
B.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
C.
regionOfHostCountry
Indicates that one entity is a geographic or administrative region belonging to, or located within, the specified host country.
-
D.
homeVenueRegion
Indicates the geographic region in which an entity’s primary or home venue is located.
-
E.
hostResidenceOf
Indicates that a location serves as the primary place of residence for a specified person or group.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7680d5c81908d6a670159879236 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:52 p.m.