Triple
T4330623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manouria tortoises |
E96738
|
entity |
| Predicate | shellDescription |
P7380
|
FINISHED |
| Object | rugged shell |
—
|
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: rugged shell | Statement: [Manouria tortoises, shellDescription, rugged shell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellDescription Context triple: [Manouria tortoises, shellDescription, rugged shell]
-
A.
shellType
chosen
Indicates the type or classification of a shell associated with an entity (e.g., its form, structure, or category).
-
B.
settingDescription
Indicates the descriptive details or characteristics that define the context or environment in which something occurs.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
commandLineTool
Indicates that an entity is a software utility intended to be executed and interacted with via a text-based command-line interface.
-
E.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514c39748190900e13e70ed8848c |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.