Triple
T1488056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys |
E29512
|
entity |
| Predicate | secondaryConstituent |
P28553
|
FINISHED |
| Object | rock |
—
|
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: rock | Statement: [Tethys, secondaryConstituent, rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryConstituent Context triple: [Tethys, secondaryConstituent, rock]
-
A.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
-
B.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
C.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
D.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
-
E.
secondTier
Indicates that something occupies a secondary or subordinate level of importance, quality, or rank relative to a primary or top tier.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a44efc819084254614d8ea4669 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52c703c8190a56389b09d97659f |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:12 p.m.