Triple
T23043709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pied kingfisher |
E573813
|
entity |
| Predicate | femaleMarkings |
P1333
|
FINISHED |
| Object | broken or single breast band |
—
|
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: broken or single breast band | Statement: [Pied kingfisher, femaleMarkings, broken or single breast band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: femaleMarkings Context triple: [Pied kingfisher, femaleMarkings, broken or single breast band]
-
A.
eggMarkings
Indicates that one entity bears or displays specific markings or patterns on its eggs in relation to another entity or context.
-
B.
originalTailMarkings
Indicates that an entity possesses or is associated with the initial or native markings found on a tail, prior to any changes or modifications.
-
C.
wingColorFemale
Indicates that the relationship specifies the color of the wings of a female individual.
-
D.
sexualDimorphism
chosen
Indicates differences in physical characteristics between males and females of a species that are systematically associated with their sex.
-
E.
leafMarkings
Indicates the presence, pattern, or characteristics of markings found on the surface of a leaf.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18517083c8190a0850da5440e0a73 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.