Triple
T26962741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pheucticus ludovicianus |
E679088
|
entity |
| Predicate | attractsTo |
P1347
|
FINISHED |
| Object | bird feeders |
—
|
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: bird feeders | Statement: [Pheucticus ludovicianus, attractsTo, bird feeders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attractsTo Context triple: [Pheucticus ludovicianus, attractsTo, bird feeders]
-
A.
attracts
chosen
Indicates that one entity exerts a force or influence that draws another entity toward it.
-
B.
attractedFigure
Indicates that one figure is visually or emotionally drawn toward, or finds appealing, another figure.
-
C.
attractionBasedOn
Indicates a relationship where one entity is drawn to or interested in another specifically because of certain attributes, qualities, or characteristics that the latter possesses.
-
D.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
E.
unrealizedAttractionFor
Indicates a one-sided or mutual romantic or emotional attraction between entities that has not been acted upon or developed into an actual relationship.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620ede4f88190a98f91af97505663 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:33 a.m.