Triple
T13111338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alsea Highway |
E310977
|
entity |
| Predicate | followsFeatureType |
P5048
|
FINISHED |
| Object | river valley |
—
|
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: river valley | Statement: [Alsea Highway, followsFeatureType, river valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsFeatureType Context triple: [Alsea Highway, followsFeatureType, river valley]
-
A.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
C.
followsElementType
Indicates that one element type comes directly after another element type in a defined order or sequence.
-
D.
followsPlanType
Indicates that one entity adheres to, or is carried out according to, a specified type of plan.
-
E.
followsCharacterType
Indicates that one character’s behavior, role, or traits are patterned after, derived from, or constrained by a specified character type.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817e4f408190b77c198b4157d77a |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.