Triple
T34604941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrés Avelino Duarte |
E888570
|
entity |
| Predicate | landGrantType |
P67115
|
FINISHED |
| Object | Mexican land grant in California |
—
|
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: Mexican land grant in California | Statement: [Andrés Avelino Duarte, landGrantType, Mexican land grant in California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landGrantType Context triple: [Andrés Avelino Duarte, landGrantType, Mexican land grant in California]
-
A.
landGrantDesignation
Indicates that an institution has been formally designated as a land-grant institution under a land-grant program or legislation.
-
B.
landGrantField
chosen
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.
-
C.
landGrantPurpose
Indicates that a land grant is made with a specific intended purpose or use in mind.
-
D.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
E.
landGrantRecipient
Indicates that an entity is the recipient or beneficiary of a grant of land from another party or authority.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.