Triple
T8377373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verreaux's eagle |
E197608
|
entity |
| Predicate | backMarkings |
P32310
|
FINISHED |
| Object | white V-shaped patch |
—
|
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 V-shaped patch | Statement: [Verreaux's eagle, backMarkings, white V-shaped patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backMarkings Context triple: [Verreaux's eagle, backMarkings, white V-shaped patch]
-
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.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
D.
distinctiveMarking
chosen
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
E.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c094908190afe9cc54ce4f4d58 |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.