Triple
T487860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascadia |
E9918
|
entity |
| Predicate | hasConceptOrigin |
P3654
|
FINISHED |
| Object | bioregionalist thought of the late 20th century |
—
|
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: bioregionalist thought of the late 20th century | Statement: [Cascadia, hasConceptOrigin, bioregionalist thought of the late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConceptOrigin Context triple: [Cascadia, hasConceptOrigin, bioregionalist thought of the late 20th century]
-
A.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
E.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0de66308190a18503a482881cfc |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.