Triple
T23671867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black-tailed gull |
E584751
|
entity |
| Predicate | billMarkings |
P152923
|
FINISHED |
| Object | red spot on bill |
—
|
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: red spot on bill | Statement: [Black-tailed gull, billMarkings, red spot on bill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billMarkings Context triple: [Black-tailed gull, billMarkings, red spot on bill]
-
A.
coatMarkings
Indicates how an entity’s coat is patterned or marked, such as stripes, spots, or other distinctive visual markings.
-
B.
eggMarkings
Indicates that one entity bears or displays specific markings or patterns on its eggs in relation to another entity or context.
-
C.
leafMarkings
Indicates the presence, pattern, or characteristics of markings found on the surface of a leaf.
-
D.
armorMarkings
Indicates that one entity bears specific markings, patterns, or insignia on its armor in relation to another entity or context.
-
E.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b41002f881908cd744ed44b70f5d |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:50 p.m.