Triple
T630637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Pendleton, California |
E15917
|
entity |
| Predicate | previousLandUse |
P2417
|
FINISHED |
| Object | ranch land |
—
|
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: ranch land | Statement: [Camp Pendleton, California, previousLandUse, ranch land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousLandUse Context triple: [Camp Pendleton, California, previousLandUse, ranch land]
-
A.
primaryLandUse
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
B.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
-
C.
previousClassification
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
-
D.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
occupiesFormerEstateOf
Indicates that one entity currently resides in, uses, or controls a property that was previously the estate of another entity.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec171008190ab91dee86e9279af |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.