Triple
T9708777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesoarchean Era |
E234966
|
entity |
| Predicate | rockRecordIncludes |
P1326
|
FINISHED |
| Object | banded iron formations |
—
|
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: banded iron formations | Statement: [Mesoarchean Era, rockRecordIncludes, banded iron formations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rockRecordIncludes Context triple: [Mesoarchean Era, rockRecordIncludes, banded iron formations]
-
A.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
B.
rockEra
Indicates that an entity is associated with, belongs to, or occurs during the rock music era.
-
C.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
D.
hasPartInDiscography
Indicates that an entity (such as a song, album, or track) is included as a component within another entity’s discography.
-
E.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da7c6188190b086f7e411378268 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.