Triple
T12675059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaluit Airport |
E302785
|
entity |
| Predicate | serves population type |
P93194
|
FINISHED |
| Object | remote community |
—
|
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: remote community | Statement: [Jaluit Airport, serves population type, remote community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serves population type Context triple: [Jaluit Airport, serves population type, remote community]
-
A.
servicePopulationType
chosen
Indicates the type or category of population that a service is intended to serve or target.
-
B.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
C.
servesPopulationCentre
Indicates that one entity provides services or functions in support of a particular population centre.
-
D.
hadPopulationType
Indicates that an entity possessed a particular classification or type of population during a given time or context.
-
E.
hostedPopulationType
Indicates the type or category of population that is accommodated or supported by a given host entity.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.