Triple
T32713387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eretmochelys imbricata |
E836456
|
entity |
| Predicate | hasShellPattern |
P8151
|
FINISHED |
| Object | amber and brown mottled pattern |
—
|
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: amber and brown mottled pattern | Statement: [Eretmochelys imbricata, hasShellPattern, amber and brown mottled pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShellPattern Context triple: [Eretmochelys imbricata, hasShellPattern, amber and brown mottled pattern]
-
A.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
B.
hasExpansionPattern
Indicates that an entity follows or is associated with a specific pattern or manner of expansion.
-
C.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
-
D.
hasStartPattern
Indicates that something begins with, or is characterized at its outset by, a specified pattern.
-
E.
hasMatch
Indicates that one entity corresponds to, aligns with, or is considered an equivalent or suitable counterpart to 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:11 a.m.