Triple
T798855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Rosa Island |
E17082
|
entity |
| Predicate | previouslyUsedFor |
P2417
|
FINISHED |
| Object | cattle ranching |
—
|
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: cattle ranching | Statement: [Santa Rosa Island, previouslyUsedFor, cattle ranching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyUsedFor Context triple: [Santa Rosa Island, previouslyUsedFor, cattle ranching]
-
A.
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.
-
B.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b4d9548190aad5fdf1211cf8cd |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.