Triple
T15888972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaenoptera acutorostrata |
E385265
|
entity |
| Predicate | flipperMarking |
P32310
|
FINISHED |
| Object | whiteBandOnFlippers |
—
|
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: whiteBandOnFlippers | Statement: [Balaenoptera acutorostrata, flipperMarking, whiteBandOnFlippers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flipperMarking Context triple: [Balaenoptera acutorostrata, flipperMarking, whiteBandOnFlippers]
-
A.
markingFeature
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
B.
eggMarkings
Indicates that one entity bears or displays specific markings or patterns on its eggs in relation to another entity or context.
-
C.
distinctiveMarking
chosen
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
D.
marque
Indicates that one entity is the brand or make associated with another entity, such as a product, vehicle, or manufactured item.
-
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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.