Triple
T35251131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angra do Heroísmo |
E1018094
|
entity |
| Predicate | elevatedToCityIn |
P3787
|
FINISHED |
| Object | 1534 |
—
|
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: 1534 | Statement: [Angra do Heroísmo, elevatedToCityIn, 1534]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToCityIn Context triple: [Angra do Heroísmo, elevatedToCityIn, 1534]
-
A.
elevatedToDistrictOf
Indicates that an entity has been officially upgraded in status or administrative level to become a district of another entity.
-
B.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
C.
upstreamCity
Indicates that one city is located upstream along a river or waterway relative to another city.
-
D.
representedCity
Indicates that an entity serves as the official representative or proxy for a particular city.
-
E.
locatedInCityWithSignificance
Indicates that an entity is located in a city that holds particular importance or notable significance (e.g., historical, cultural, political, or economic).
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:02 p.m.