Triple
T31047358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazonian craton |
E791164
|
entity |
| Predicate | hasBeenLinkedTo |
P180731
|
FINISHED |
| Object | supercontinent Rodinia |
—
|
NE NERFINISHED |
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: supercontinent Rodinia | Statement: [Amazonian craton, hasBeenLinkedTo, supercontinent Rodinia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenLinkedTo Context triple: [Amazonian craton, hasBeenLinkedTo, supercontinent Rodinia]
-
A.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
B.
hasPaidLinkTo
Indicates that one entity includes a hyperlink to another entity in exchange for payment or other compensation.
-
C.
linkedByServiceTo
Indicates that one entity is connected or associated with another through a specific service acting as the linking mechanism.
-
D.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
E.
hasCommunityLink
Indicates that there exists an established connection or association between an entity and a community.
- F. None of above. chosen
Provenance (4 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 29, 2026, 8:59 p.m.