Triple
T24808096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elena García |
E620707
|
entity |
| Predicate | hasDiacriticInSurname |
P2270
|
FINISHED |
| Object | í in García |
—
|
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: í in García | Statement: [Elena García, hasDiacriticInSurname, í in García]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiacriticInSurname Context triple: [Elena García, hasDiacriticInSurname, í in García]
-
A.
hasCharacterWithSurname
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
-
B.
usesDiacritics
chosen
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
C.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
D.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
-
E.
usesDiacriticsFrom
Indicates that one entity employs or incorporates the diacritical marks that originate from or are characteristic of 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 4:50 a.m.