Triple
T4330647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manouria tortoises |
E96738
|
entity |
| Predicate | shellFunction |
P30862
|
FINISHED |
| Object | protection from predators |
—
|
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: protection from predators | Statement: [Manouria tortoises, shellFunction, protection from predators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellFunction Context triple: [Manouria tortoises, shellFunction, protection from predators]
-
A.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
B.
functionInSystem
chosen
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
C.
houseFunction
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
D.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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.