Triple
T38388518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibéria |
E899644
|
entity |
| Predicate | countryOfCulturalReference |
P26995
|
FINISHED |
| Object | Spain |
E3665
|
NE 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: Spain | Statement: [Ibéria, countryOfCulturalReference, Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfCulturalReference Context triple: [Ibéria, countryOfCulturalReference, Spain]
-
A.
countryOfCulturalSignificance
chosen
Indicates that a country holds notable cultural importance or influence for a given entity, such as a person, group, object, or practice.
-
B.
countryOfCult
Indicates that a particular cult, religious group, or worship practice is associated with, originates from, or is primarily practiced in a specific country.
-
C.
cultureOfOrigin
Indicates the cultural background or tradition from which an entity originates or is derived.
-
D.
continentOfCulturalContext
Indicates that a cultural context is associated with, originates from, or is primarily situated within a specific continent.
-
E.
countryOfReferent
Indicates that one entity is the country with which the referenced entity (the referent) is associated or to which it belongs.
- F. None of above.
Provenance (4 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b2990d5481909ee01803cc1c0649 |
completed | June 28, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.