Triple
T32037470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fono building |
E818132
|
entity |
| Predicate | locatedInTerritorialCapital |
P5025
|
FINISHED |
| Object | Pago Pago |
E7953
|
NE 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: Pago Pago | Statement: [Fono building, locatedInTerritorialCapital, Pago Pago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTerritorialCapital Context triple: [Fono building, locatedInTerritorialCapital, Pago Pago]
-
A.
locatedInCapital
chosen
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
-
B.
locatedInNationCapitalRegion
Indicates that an entity is situated within the capital region of a specific nation.
-
C.
locatedInCapitalCityPort
Indicates that something is situated within the port area of a country's capital city.
-
D.
locatedInCountryCapitalOfProvince
Indicates that an entity is located in the country that contains the capital city of a specified province.
-
E.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
- F. None of above.
Provenance (4 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a020ec13d808190b41acdc31adc4191 |
completed | May 11, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2edddaa0908190b626b1607183544b |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a020d9259c08190ad0370091c23ea8a |
completed | May 11, 2026, 5:10 p.m. |
Created at: May 1, 2026, 12:19 a.m.