Triple
T11304532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fishways at Hell's Gate |
E267679
|
entity |
| Predicate | servesSpecies |
P48322
|
FINISHED |
| Object | Pacific salmon |
—
|
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: Pacific salmon | Statement: [fishways at Hell's Gate, servesSpecies, Pacific salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesSpecies Context triple: [fishways at Hell's Gate, servesSpecies, Pacific salmon]
-
A.
animalTypeServed
Indicates the type or category of animal that is provided or served in a given context.
-
B.
servesType
chosen
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
C.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
D.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
E.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a7255c81909675fe9ad6d71934 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.