Triple
T38237928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anserinae |
E1013673
|
entity |
| Predicate | includesBirdType |
P204560
|
FINISHED |
| Object | migratory waterfowl |
—
|
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: migratory waterfowl | Statement: [Anserinae, includesBirdType, migratory waterfowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBirdType Context triple: [Anserinae, includesBirdType, migratory waterfowl]
-
A.
hasBirdSpecies
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
-
B.
typicalBird
Indicates that the subject is considered a representative or standard example of a bird, exhibiting the common or characteristic features associated with birds.
-
C.
birdFamily
Indicates that one entity belongs to, or is classified within, the same bird family as another entity.
-
D.
birdRepresents
Indicates that one bird stands for, symbolizes, or serves as a representation of another entity in some context.
-
E.
isBirdLike
Indicates that one entity resembles or shares key characteristics or behaviors with birds.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.