Triple
T29179649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zagros orogeny |
E739710
|
entity |
| Predicate | intensified |
P12654
|
FINISHED |
| Object | Cenozoic |
—
|
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: Cenozoic | Statement: [Zagros orogeny, intensified, Cenozoic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intensified Context triple: [Zagros orogeny, intensified, Cenozoic]
-
A.
intensifiedOver
Indicates that one entity increases the degree, strength, or intensity of another entity or condition beyond its previous level.
-
B.
moreIntenseThan
Indicates that one entity exhibits a greater degree or strength of a particular quality, effect, or activity than another entity.
-
C.
significantlyIntensifiedAfter
Indicates that one condition, effect, or quality became much stronger or more pronounced following another event or state.
-
D.
eraOfIncreasedIntensity
chosen
Indicates a period during which the level or strength of a particular activity, condition, or phenomenon becomes significantly higher than before.
-
E.
isIntense
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 11:56 a.m.