Triple
T33091289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alofi North |
E846787
|
entity |
| Predicate | sharesCapitalAreaWith |
P23812
|
FINISHED |
| Object | Alofi South |
—
|
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: Alofi South | Statement: [Alofi North, sharesCapitalAreaWith, Alofi South]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCapitalAreaWith Context triple: [Alofi North, sharesCapitalAreaWith, Alofi South]
-
A.
sharesArealFeaturesWith
Indicates that two entities possess similar or overlapping spatial or geographic characteristics.
-
B.
sharesAreaWith
chosen
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
C.
sharesBorderWithSector
Indicates that one sector directly touches and has a common boundary line with another sector.
-
D.
sharesBusinessParkWith
Indicates that two entities are located in and operate from the same business park complex.
-
E.
sharesHeadquartersWith
Indicates that two entities have their main headquarters located in the same place.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 1, 2026, 1:26 a.m.