Triple
T9506745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pannotia |
E229288
|
entity |
| Predicate | assemblyProcess |
P19323
|
FINISHED |
| Object | collision and amalgamation of Neoproterozoic cratons |
—
|
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: collision and amalgamation of Neoproterozoic cratons | Statement: [Pannotia, assemblyProcess, collision and amalgamation of Neoproterozoic cratons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblyProcess Context triple: [Pannotia, assemblyProcess, collision and amalgamation of Neoproterozoic cratons]
-
A.
assemblyRequired
Indicates that the associated item or components must be put together or constructed before they can be used.
-
B.
assemblyState
Indicates the current configuration or completeness status of an object or system in its assembly process.
-
C.
assemblySegments
Indicates that an entity is composed of or associated with specific component segments that together form its assembly.
-
D.
assemblyLinkedTo
Indicates that one assembly is associated or connected to another assembly in a meaningful or functionally relevant way.
-
E.
assembly
chosen
Indicates that one entity is composed of, constructed from, or formed by putting together multiple other entities or components.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98543b1881908b537abdc1d2f9c0 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.