Triple
T8519984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Triassic |
E201670
|
entity |
| Predicate | hasColorOnGeologicChart |
P22465
|
FINISHED |
| Object | light green |
—
|
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: light green | Statement: [Middle Triassic, hasColorOnGeologicChart, light green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorOnGeologicChart Context triple: [Middle Triassic, hasColorOnGeologicChart, light green]
-
A.
hasGeologicalSignificance
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
-
B.
geologicalStatus
Indicates the current geological condition or classification of an entity, such as its formation state, activity level, or structural status within the Earth’s crust.
-
C.
hasSoilColor
Indicates that an entity possesses soil characterized by a specific color.
-
D.
hasGeologicResource
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
E.
hasColoration
chosen
Indicates that an entity possesses a particular color or pattern of colors.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe628f8c48190a35201f9fde605cc |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.