Triple
T2579846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White bass |
E57061
|
entity |
| Predicate | targetedWith |
P35065
|
FINISHED |
| Object | jigs |
—
|
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: jigs | Statement: [White bass, targetedWith, jigs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedWith Context triple: [White bass, targetedWith, jigs]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
targetedCondition
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
C.
targetedActivity
chosen
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
D.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
E.
wasTargetDuring
Indicates that an entity served as the target of another entity or action during a specified time period or event.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a9fd3c8190a521931e40cd801c |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.