Triple
T37271348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De la Isla |
E924520
|
entity |
| Predicate | refersToOriginType |
P106458
|
FINISHED |
| Object | island |
—
|
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: island | Statement: [De la Isla, refersToOriginType, island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToOriginType Context triple: [De la Isla, refersToOriginType, island]
-
A.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
C.
hasNameOriginType
chosen
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
D.
possibleTypeOfReferent
Indicates that something could be a potential or candidate type or category to which a given referent may belong, without asserting that it definitively is that type.
-
E.
classOrigin
Indicates the original class or category from which an entity is derived, instantiated, or classified.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:15 p.m.