Triple
T27990391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearblossom Hwy., 11–18th April 1986, #2 |
E706853
|
entity |
| Predicate | state of location depicted |
P182751
|
FINISHED |
| Object | California |
—
|
NE NERFINISHED |
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: California | Statement: [Pearblossom Hwy., 11–18th April 1986, #2, state of location depicted, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: state of location depicted Context triple: [Pearblossom Hwy., 11–18th April 1986, #2, state of location depicted, California]
-
A.
location depicted
Indicates that one entity visually represents or shows the place where another entity is situated or occurs.
-
B.
portrayedByRealWorldLocation
Indicates that a fictional or represented location is depicted or substituted by an actual real-world location.
-
C.
positionDepicted
Indicates that one entity visually represents or depicts the spatial position or placement of another entity.
-
D.
locationPresented
Indicates that a specific location is presented or shown to an entity (such as a user or system) within a given context.
-
E.
showLocation
Indicates that one entity displays or reveals the position or place of 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: April 27, 2026, 7:49 p.m.