Triple
T1079287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vredefort Dome |
E23910
|
entity |
| Predicate | oldestOfType |
P7751
|
FINISHED |
| Object | one of the oldest known impact structures on Earth |
—
|
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: one of the oldest known impact structures on Earth | Statement: [Vredefort Dome, oldestOfType, one of the oldest known impact structures on Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldestOfType Context triple: [Vredefort Dome, oldestOfType, one of the oldest known impact structures on Earth]
-
A.
isOldest
chosen
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
B.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
-
C.
isYoungestOf
Indicates that the subject is the youngest member within the specified group or set of related entities.
-
D.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
E.
earliestKnownHolder
Indicates that the subject is the first known entity in time to have possessed, held, or been assigned the object.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b943b41481909b24050ca7e78971 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.