Triple
T34604942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrés Avelino Duarte |
E888570
|
entity |
| Predicate | landGrantName |
P179747
|
FINISHED |
| Object | Rancho Azusa de Duarte |
—
|
NE NERFINISHED |
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: Rancho Azusa de Duarte | Statement: [Andrés Avelino Duarte, landGrantName, Rancho Azusa de Duarte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landGrantName Context triple: [Andrés Avelino Duarte, landGrantName, Rancho Azusa de Duarte]
-
A.
landGrantField
Indicates that a specific field or parcel of land has been allocated or granted, typically by an authority, to a recipient under a land grant arrangement.
-
B.
landGrantDesignation
Indicates that an institution has been formally designated as a land-grant institution under a land-grant program or legislation.
-
C.
landGrantLocation
Indicates the geographic place or area to which a particular land grant applies or in which it is situated.
-
D.
landGrantRecipient
Indicates that an entity is the recipient or beneficiary of a grant of land from another party or authority.
-
E.
originalLandGrantBy
Indicates that an entity was granted land by a specified grantor in the original land grant transaction.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727bd39b081908457590c3ba9b745 |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 2:03 a.m.