Triple
T19127429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saharan Metacraton |
E468221
|
entity |
| Predicate | reworkedDuring |
P98606
|
FINISHED |
| Object | Neoproterozoic |
—
|
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: Neoproterozoic | Statement: [Saharan Metacraton, reworkedDuring, Neoproterozoic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reworkedDuring Context triple: [Saharan Metacraton, reworkedDuring, Neoproterozoic]
-
A.
reworkedBy
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
B.
reconstructedDuring
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
-
C.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
D.
modifiedDuring
chosen
Indicates that one entity underwent a change or alteration while another specified time period, process, or event was occurring.
-
E.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, another entity.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cd851081909d5665b362ae08de |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.