Triple
T27909275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red-footed booby |
E705875
|
entity |
| Predicate | plumageMorph |
P163764
|
FINISHED |
| Object | white-tailed brown 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: white-tailed brown morph | Statement: [red-footed booby, plumageMorph, white-tailed brown morph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plumageMorph Context triple: [red-footed booby, plumageMorph, white-tailed brown morph]
-
A.
plumageMorph
chosen
Indicates a relationship where an entity is characterized by a particular form or variant of plumage.
-
B.
plumageFeature
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
C.
plumageDimorphism
Indicates that there is a difference in plumage characteristics between two groups (typically sexes or age classes) within a species.
-
D.
plumageMarkingsColor
Indicates the color of the markings or patterns present on an entity's plumage.
-
E.
plumageColorSource
Indicates the relationship by which the color of an entity’s plumage is derived from or attributed to a particular source.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 6:48 p.m.