Triple
T29044889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huemul Island |
E738105
|
entity |
| Predicate | hasLaterUsePeriod |
P5014
|
FINISHED |
| Object | tourism and recreation after project closure |
—
|
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: tourism and recreation after project closure | Statement: [Huemul Island, hasLaterUsePeriod, tourism and recreation after project closure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterUsePeriod Context triple: [Huemul Island, hasLaterUsePeriod, tourism and recreation after project closure]
-
A.
hasPeriodOf
Indicates that one entity possesses, experiences, or is associated with a specific span or interval of time.
-
B.
subsequentUse
chosen
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
C.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
hasSecondaryPeriod
Indicates that an entity is associated with an additional, subordinate, or second time period beyond its primary period.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 10:04 a.m.