Triple
T26301486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamarán |
E661569
|
entity |
| Predicate | hasHistoricalUseAs |
P29363
|
FINISHED |
| Object | name of Gran Canaria |
—
|
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: name of Gran Canaria | Statement: [Tamarán, hasHistoricalUseAs, name of Gran Canaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalUseAs Context triple: [Tamarán, hasHistoricalUseAs, name of Gran Canaria]
-
A.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
-
B.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
C.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
D.
hasFormerUse
chosen
Indicates that something previously served a particular function or role that it no longer has.
-
E.
hasPrimaryUseHistoric
Indicates that something is primarily used for historic or heritage-related purposes.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 26, 2026, 10:16 p.m.