Triple
T802129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Alta California |
E17150
|
entity |
| Predicate | landPolicy |
P21194
|
FINISHED |
| Object | Mexican land grant (ranchos) system |
—
|
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 (ranchos) system | Statement: [Mexican Alta California, landPolicy, Mexican land grant (ranchos) system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landPolicy Context triple: [Mexican Alta California, landPolicy, Mexican land grant (ranchos) system]
-
A.
legalArea
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
B.
landComponent
Indicates that one entity is a physical land portion or segment that forms part of a larger land area or land-related whole.
-
C.
estate
Indicates a legal or ownership relationship in which a person or entity holds rights, interests, or control over property or assets.
-
D.
landholdings
Indicates the extent or collection of land owned, controlled, or held by an entity.
-
E.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
| PDg | Predicate description generation | batch_69a4ace369b481908ad69de6de99f5e6 |
completed | March 1, 2026, 9:17 p.m. |
Created at: March 1, 2026, 7:38 p.m.