Triple
T31250354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Howe Island–Sydney |
E796797
|
entity |
| Predicate | remoteAreaServed |
P131382
|
FINISHED |
| Object | Lord Howe Island |
—
|
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: Lord Howe Island | Statement: [Lord Howe Island–Sydney, remoteAreaServed, Lord Howe Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remoteAreaServed Context triple: [Lord Howe Island–Sydney, remoteAreaServed, Lord Howe Island]
-
A.
servesRemoteArea
chosen
Indicates that an entity provides services or support to people or locations in geographically remote or hard-to-reach areas.
-
B.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
-
D.
remoteArea
Indicates that an entity is located in or associated with a geographically isolated or sparsely populated area far from urban centers.
-
E.
areaServedType
Indicates the type or category of area that is served by an entity or service.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.