Triple
T32713414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eretmochelys imbricata |
E836456
|
entity |
| Predicate | shellUseByHumans |
P174835
|
FINISHED |
| Object | tortoiseshell products |
—
|
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: tortoiseshell products | Statement: [Eretmochelys imbricata, shellUseByHumans, tortoiseshell products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellUseByHumans Context triple: [Eretmochelys imbricata, shellUseByHumans, tortoiseshell products]
-
A.
shellFeature
Indicates that one entity functions as a characteristic or structural feature of another entity’s shell.
-
B.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
C.
shellType
Indicates the type or classification of a shell associated with an entity (e.g., its form, structure, or category).
-
D.
usageInstruction
Indicates that one entity provides guidance or directions on how to properly use, operate, or handle another entity.
-
E.
commandSyntax
Indicates the specific structure or format in which a command must be written or expressed.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c883541c8190abff705a5658bc68 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:11 a.m.