Triple
T33138156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lasqueti Island |
E848067
|
entity |
| Predicate | hasLimitedServices |
P115196
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lasqueti Island, hasLimitedServices, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedServices Context triple: [Lasqueti Island, hasLimitedServices, true]
-
A.
hasLimitedServiceType
Indicates that an entity is associated with a service that is restricted in scope, availability, or functionality compared to full or standard service types.
-
B.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
C.
hasCommunicationLimitation
Indicates that an entity is subject to some restriction, constraint, or reduced capacity in its ability to communicate.
-
D.
hasLimitedFacilities
chosen
Indicates that an entity provides only a restricted or insufficient range or quality of facilities or services.
-
E.
hasLimitedWeekdayService
Indicates that the service operates on weekdays only during restricted or reduced hours or on a limited schedule.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 1:27 a.m.