Triple
T24251680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | María García |
E603542
|
entity |
| Predicate | isUsedInOfficialDocuments |
P24110
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [María García, isUsedInOfficialDocuments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInOfficialDocuments Context triple: [María García, isUsedInOfficialDocuments, yes]
-
A.
usedInOfficialDocumentsOf
Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity or jurisdiction.
-
B.
hasOfficialUse
chosen
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
C.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
D.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
E.
usedInFinancialDocuments
Indicates that something is employed or appears within financial documents or records.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b89eb8081909ccf37081add5cee |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.