Triple
T7285364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolmanskop |
E163851
|
entity |
| Predicate | discoveredResource |
P75389
|
FINISHED |
| Object | diamonds |
—
|
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: diamonds | Statement: [Kolmanskop, discoveredResource, diamonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredResource Context triple: [Kolmanskop, discoveredResource, diamonds]
-
A.
discoveredFeature
Indicates that an entity has identified or uncovered a previously unknown or unrecognized feature of another entity or object.
-
B.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
C.
discoveredArtifact
Indicates that an entity has found or uncovered a previously unknown or hidden artifact.
-
D.
discoveredWith
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
-
E.
discoveredAsPartOf
Indicates that something was found, identified, or revealed in the course of a larger activity, process, or investigation of which it formed a component.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb51a8bc8190a3e1ec09ee1aeb38 |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e82b0f9881909d29c99af1ea0dbf |
completed | March 27, 2026, 8:27 p.m. |
Created at: March 27, 2026, 2:59 p.m.