Triple
T23092262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonio García |
E575789
|
entity |
| Predicate | hasPossibleFullNamePattern |
P8151
|
FINISHED |
| Object | Antonio García [second surname] |
—
|
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: Antonio García [second surname] | Statement: [Antonio García, hasPossibleFullNamePattern, Antonio García [second surname]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleFullNamePattern Context triple: [Antonio García, hasPossibleFullNamePattern, Antonio García [second surname]]
-
A.
hasSurnamePattern
Indicates that an entity’s surname follows or matches a specified structural or stylistic pattern.
-
B.
hasFullNameUsage
Indicates that an entity uses a particular full name in a specific context or manner.
-
C.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
D.
hasFullNameReference
Indicates that one entity serves as a complete, explicit name or designation referring to another entity.
-
E.
hasAbbreviationPattern
Indicates that there is a systematic abbreviation relationship between two strings, where one follows a recognizable pattern derived from the other.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18dab3798819081b2b46a20751b2a |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.