Triple
T33895282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedo de Deus |
E868890
|
entity |
| Predicate | hasRockFace |
P196296
|
FINISHED |
| Object | steep granite walls |
—
|
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: steep granite walls | Statement: [Dedo de Deus, hasRockFace, steep granite walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockFace Context triple: [Dedo de Deus, hasRockFace, steep granite walls]
-
A.
hasRock
Indicates that one entity possesses, contains, or is associated with a rock.
-
B.
hasFace
Indicates that one entity possesses, displays, or is characterized by a face.
-
C.
hasRockRecordIn
Indicates that an entity has a recorded instance or documentation of rock-related data, activity, or presence within a specified context or location.
-
D.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
E.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69fe1fd58ad8819093d3d705e8521014 |
completed | May 8, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:48 a.m.