Triple
T26844377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gómez |
E675874
|
entity |
| Predicate | hasFrequencyCategoryInSpain |
P39630
|
FINISHED |
| Object | very common |
—
|
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: very common | Statement: [Gómez, hasFrequencyCategoryInSpain, very common]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrequencyCategoryInSpain Context triple: [Gómez, hasFrequencyCategoryInSpain, very common]
-
A.
frequencyCategoryInSpain
chosen
Indicates the categorized level of how often something occurs or is observed within Spain.
-
B.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
C.
hasApproximateEuropeanFrequency
Indicates that the subject has an estimated or approximate occurrence rate within European populations.
-
D.
statusInSpain
Indicates the legal, social, or official condition or standing that an entity has within the jurisdiction of Spain.
-
E.
hasFrequencyCoverage
Indicates that one entity provides, supports, or is applicable across a specified range or set of frequencies associated with another entity.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 5:10 a.m.