Triple
T27758171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erythrura gouldiae |
E701387
|
entity |
| Predicate | headColorMorph |
P31412
|
FINISHED |
| Object | yellow-headed morph |
—
|
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: yellow-headed morph | Statement: [Erythrura gouldiae, headColorMorph, yellow-headed morph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headColorMorph Context triple: [Erythrura gouldiae, headColorMorph, yellow-headed morph]
-
A.
headColor
chosen
Indicates the color attribute specifically associated with the head of an entity.
-
B.
headAppearance
Indicates how an entity’s head looks or is visually characterized, such as its shape, features, or notable attributes.
-
C.
headShape
Indicates the characteristic form or contour of an entity’s head.
-
D.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
E.
headProportion
Indicates the proportional relationship between the size of an entity’s head and a reference measure, such as its body or overall height.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 4:24 p.m.