Triple
T28620473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA 178 |
E724367
|
entity |
| Predicate | namedAfterFeature |
P63
|
FINISHED |
| Object | Kern River (for canyon segment) |
—
|
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: Kern River (for canyon segment) | Statement: [CA 178, namedAfterFeature, Kern River (for canyon segment)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterFeature Context triple: [CA 178, namedAfterFeature, Kern River (for canyon segment)]
-
A.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
C.
namedForFeature
Indicates that one entity is named after, or derives its name from, a particular feature or characteristic of another entity.
-
D.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
E.
namedAfterField
Indicates that one entity has been given a name derived from or in honor of another entity, typically a person, place, or thing.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 4:33 a.m.