Triple
T37076448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | radiated tortoise |
E917722
|
entity |
| Predicate | carapaceMarkings |
P117162
|
FINISHED |
| Object | yellow radiating lines on each scute |
—
|
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: yellow radiating lines on each scute | Statement: [radiated tortoise, carapaceMarkings, yellow radiating lines on each scute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carapaceMarkings Context triple: [radiated tortoise, carapaceMarkings, yellow radiating lines on each scute]
-
A.
carapaceCharacteristic
chosen
Indicates that one entity has a specific feature, quality, or attribute of its carapace in relation to another 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.
hasCarapace
Indicates that an entity possesses a hard, protective outer shell or covering (a carapace).
-
D.
carapaceLength
Indicates the measured length of an organism’s carapace from a defined anatomical reference point.
-
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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.