Triple
T27758219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidua finches |
E701388
|
entity |
| Predicate | hostChickCompetition |
P165409
|
FINISHED |
| Object | competes with host nestlings for food |
—
|
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: competes with host nestlings for food | Statement: [Vidua finches, hostChickCompetition, competes with host nestlings for food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostChickCompetition Context triple: [Vidua finches, hostChickCompetition, competes with host nestlings for food]
-
A.
hostTournaments
Indicates that an entity organizes and provides the venue or platform for tournaments to take place.
-
B.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
C.
tournamentHost
Indicates that one entity serves as the organizer or official host of a tournament involving the other entity.
-
D.
coHostNation
Indicates that a nation shares the role and responsibilities of hosting a particular event, typically alongside one or more other nations.
-
E.
hostCeremony
Indicates that one entity organizes and conducts a formal event or ceremony for or involving another entity.
- F. None of above. chosen
Provenance (4 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 4:25 p.m.