Triple
T17086630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thelodonti |
E414614
|
entity |
| Predicate | scaleFunction |
P125831
|
FINISHED |
| Object | protection |
—
|
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 | Statement: [Thelodonti, scaleFunction, protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleFunction Context triple: [Thelodonti, scaleFunction, protection]
-
A.
scaleProperty
Indicates that one entity defines or modifies the scale, magnitude, or proportional sizing used to interpret or represent a property of another entity.
-
B.
scalingProperty
Indicates how a quantity or behavior changes in proportion to changes in another variable, typically under resizing or rescaling conditions.
-
C.
scaleDefinition
Indicates that an entity specifies the parameters, structure, or measurement system used to define a particular scale.
-
D.
scaleRelation
Indicates a relationship where one quantity, object, or representation is proportionally larger or smaller than another according to a specific scale or factor.
-
E.
scalePosition
Indicates the relative location or index of an element within a defined scale or ordered measurement framework.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe7ccb48190b8fb39e2a0ba0782 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.