Triple
T1079286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vredefort Dome |
E23910
|
entity |
| Predicate | largestOfType |
P4495
|
FINISHED |
| Object | largest known impact structure 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: largest known impact structure on Earth | Statement: [Vredefort Dome, largestOfType, largest known impact structure on Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestOfType Context triple: [Vredefort Dome, largestOfType, largest known impact structure on Earth]
-
A.
isLargestOf
chosen
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
B.
largerThan
Indicates that one entity has a greater size, extent, or magnitude than another entity.
-
C.
createdOneOfLargest
Indicates that an entity is responsible for creating something that ranks among the largest within a given group or category.
-
D.
maximumVesselType
Indicates the highest or largest class, size, or category of vessel that is allowed, applicable, or associated in a given context.
-
E.
isThirdLargestIn
Indicates that an entity ranks as the third largest member within a specified group or set based on size or magnitude.
- 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.