Triple
T19229085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tithonium Chasma |
E480819
|
entity |
| Predicate | hasLaterModificationAge |
P128878
|
FINISHED |
| Object | Amazonian |
—
|
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: Amazonian | Statement: [Tithonium Chasma, hasLaterModificationAge, Amazonian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterModificationAge Context triple: [Tithonium Chasma, hasLaterModificationAge, Amazonian]
-
A.
laterModifiedIn
chosen
Indicates that one entity was modified at a later time than another entity within the same context or sequence.
-
B.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
-
C.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
D.
laterModifiedTo
Indicates that an entity was changed or updated at a later time into another specified form or state.
-
E.
hasAlterationPeriod
Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9be0d08190afe6040e0cf9c737 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:25 p.m.