Triple
T30768236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabrillo Canyon |
E783435
|
entity |
| Predicate | hasNotableStructureAbove |
P8273
|
FINISHED |
| Object | Cabrillo Bridge |
—
|
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: Cabrillo Bridge | Statement: [Cabrillo Canyon, hasNotableStructureAbove, Cabrillo Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableStructureAbove Context triple: [Cabrillo Canyon, hasNotableStructureAbove, Cabrillo Bridge]
-
A.
hasStructureAbove
chosen
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
B.
hasNotableStructureOn
Indicates that a subject entity possesses or features a significant or noteworthy structure located on it.
-
C.
hasNotableParent
Indicates that an entity has a parent who is distinguished, prominent, or otherwise notable.
-
D.
hasNotableDescendant
Indicates that an entity has at least one descendant who is recognized as notable or significant in some context.
-
E.
hasLandmarkAbove
Indicates that one landmark is positioned vertically higher than another within a given spatial or anatomical reference frame.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
Created at: April 29, 2026, 8:40 p.m.