Triple
T34571690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrapin |
E887641
|
entity |
| Predicate | hasShellFunction |
P9243
|
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: [Terrapin, hasShellFunction, protection from predators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShellFunction Context triple: [Terrapin, hasShellFunction, protection from predators]
-
A.
hasShell
chosen
Indicates that an entity possesses or is covered by a shell as a physical protective structure.
-
B.
hasCoreFunction
Indicates that one entity serves as a primary or essential function or role of another entity.
-
C.
hasUserFunction
Indicates that an entity is associated with, or assigned, a particular user-related role, capability, or function.
-
D.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
E.
hasHubFunction
Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 2:03 a.m.