Triple
T31666029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kibaran orogeny |
E808126
|
entity |
| Predicate | hasRockRecordIn |
P193609
|
FINISHED |
| Object | Kibara Belt |
—
|
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: Kibara Belt | Statement: [Kibaran orogeny, hasRockRecordIn, Kibara Belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockRecordIn Context triple: [Kibaran orogeny, hasRockRecordIn, Kibara Belt]
-
A.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
B.
hasRockSequence
Indicates that one entity possesses or is associated with a specific ordered sequence of rocks.
-
C.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
D.
hasRockGrade
Indicates that an entity is associated with a specific difficulty or quality grade used to classify rock climbing routes or rock features.
-
E.
hasRockSubgenre
Indicates a relationship where one musical style is classified as a subgenre within the broader category of rock music.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: April 30, 2026, 10:59 p.m.