Triple
T19085670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharks |
E467141
|
entity |
| Predicate | toothReplacement |
P134319
|
FINISHED |
| Object | continuous throughout life |
—
|
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: continuous throughout life | Statement: [Sharks, toothReplacement, continuous throughout life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toothReplacement Context triple: [Sharks, toothReplacement, continuous throughout life]
-
A.
hasProsthesis
Indicates that an entity possesses or is equipped with an artificial substitute for a missing or impaired body part.
-
B.
primaryReplacementFor
Indicates that one entity serves as the main or preferred substitute or successor for another entity.
-
C.
replacedPartOf
Indicates that one entity has taken the place of another entity as a component or part within a larger whole.
-
D.
developedAsReplacementFor
Indicates that one entity was created or designed specifically to take the place of another entity, serving as its successor or substitute.
-
E.
replacedInNewDesignsBy
Indicates that an element or component is superseded and functionally taken over by another element or component in newer designs.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e346f57c8190a6299e09a0be9e05 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.