Triple
T18677965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | redear sunfish |
E456650
|
entity |
| Predicate | preferredBait |
P12179
|
FINISHED |
| Object | worms |
—
|
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: worms | Statement: [redear sunfish, preferredBait, worms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredBait Context triple: [redear sunfish, preferredBait, worms]
-
A.
lures
Indicates that one entity attracts, entices, or draws another entity toward itself, often by offering something appealing or deceptive.
-
B.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
C.
fishedFor
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
-
D.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
E.
favored
chosen
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b66680819082a268f1bf857db5 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.