Triple
T37606098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beagle Bay |
E935654
|
entity |
| Predicate | hasOutstation |
P113639
|
FINISHED |
| Object | Billard community |
—
|
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: Billard community | Statement: [Beagle Bay, hasOutstation, Billard community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutstation Context triple: [Beagle Bay, hasOutstation, Billard community]
-
A.
hasOutstations
chosen
Indicates that an entity maintains or is associated with one or more subsidiary locations or branches situated away from its main base or headquarters.
-
B.
hasDomesticTerminal
Indicates that a transportation facility, typically an airport, includes a terminal dedicated to domestic (within-country) travel operations.
-
C.
hasCrossBorderCommuting
Indicates that there is a regular pattern of commuting across national borders between the related entities.
-
D.
hasVacationHomeLocation
Indicates that an entity owns or uses a vacation home that is located in a specified place.
-
E.
isRemoteFromMainland
Indicates that a location is geographically separated and distant from the primary mainland area of a region or country.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.