Triple
T27326424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderbury Island |
E689661
|
entity |
| Predicate | condominiumAdministeredBy |
P86
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Enderbury Island, condominiumAdministeredBy, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: condominiumAdministeredBy Context triple: [Enderbury Island, condominiumAdministeredBy, United Kingdom]
-
A.
isCondominium
Indicates that the subject property is classified or structured as a condominium.
-
B.
managesPropertyFor
Indicates that one entity is responsible for overseeing, operating, or administering a property on behalf of another entity.
-
C.
managementCompany
Indicates that one entity serves as the managing company responsible for overseeing or administering another entity.
-
D.
homeAssociation
Indicates a relationship where one entity is associated with, belongs to, or is linked as a home or primary place to another entity.
-
E.
administeredBy
chosen
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627edd6d08190a059d44edecfb368 |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:36 a.m.