Triple
T6095569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernardo de Gálvez |
E135867
|
entity |
| Predicate | dateReceived |
P68092
|
FINISHED |
| Object | Honorary U.S. citizenship:2014-12-16 |
—
|
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: Honorary U.S. citizenship:2014-12-16 | Statement: [Bernardo de Gálvez, dateReceived, Honorary U.S. citizenship:2014-12-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateReceived Context triple: [Bernardo de Gálvez, dateReceived, Honorary U.S. citizenship:2014-12-16]
-
A.
dateSent
Indicates the specific date on which something (such as a message, document, or item) was sent from one party to another.
-
B.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
-
E.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
- F. None of above. chosen
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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a963bac8190bc0c33fef187875c |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:12 p.m.