Triple
T8356755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pliensbachian |
E196699
|
entity |
| Predicate | environmentDominant |
P25100
|
FINISHED |
| Object | open marine shelf settings |
—
|
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: open marine shelf settings | Statement: [Pliensbachian, environmentDominant, open marine shelf settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentDominant Context triple: [Pliensbachian, environmentDominant, open marine shelf settings]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
environmentScale
Indicates the relative size, extent, or magnitude of an environment in which entities or processes exist or operate.
-
C.
environmentalFactor
Indicates that one entity functions as an environmental influence or condition that affects another entity or process.
-
D.
environmentalMedium
Indicates the environmental context or medium (such as air, water, or soil) through which a substance, effect, or process occurs or is present.
-
E.
dominantEnvironment
chosen
Indicates the primary or prevailing environment or setting in which an entity most characteristically exists, operates, or exerts influence.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.