Triple
T29669998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encruzado |
E750640
|
entity |
| Predicate | typicalMinerality |
P203805
|
FINISHED |
| Object | granite-derived mineral character |
—
|
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: granite-derived mineral character | Statement: [Encruzado, typicalMinerality, granite-derived mineral character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMinerality Context triple: [Encruzado, typicalMinerality, granite-derived mineral character]
-
A.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
B.
isMineralRich
Indicates that a location or substance contains a high concentration or abundance of minerals.
-
C.
mineralizationType
Indicates the specific kind or style of mineral deposition or ore-forming process characterizing a mineralized occurrence or deposit.
-
D.
hasMineralClass
Indicates that an entity is associated with, or categorized under, a particular mineral classification.
-
E.
isAssociatedWithMineral
Indicates that there is a relationship or connection between an entity and a specific mineral, such as composition, presence, or relevance.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a020ab9630c8190a55efd5704cc6043 |
completed | May 11, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_6a020800e2b88190a1a37e710d8c92bf |
completed | May 11, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_6a020ab8b33481908e531bb248d740ad |
completed | May 11, 2026, 4:58 p.m. |
Created at: April 28, 2026, 7:04 p.m.