Triple
T9231229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazonia |
E221819
|
entity |
| Predicate | formedBefore |
P5873
|
FINISHED |
| Object | Phanerozoic orogenic belts of South America |
—
|
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: Phanerozoic orogenic belts of South America | Statement: [Amazonia, formedBefore, Phanerozoic orogenic belts of South America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedBefore Context triple: [Amazonia, formedBefore, Phanerozoic orogenic belts of South America]
-
A.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
B.
createdBefore
chosen
Indicates that one entity was created at an earlier time than another entity.
-
C.
formedBetween
Indicates a relationship in which a connection, bond, or structure has come into existence linking two or more entities.
-
D.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee190204819096b38270a0abc116 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.