Triple
T36557745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grey Mountains |
E901739
|
entity |
| Predicate | knownForResource |
P75389
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Grey Mountains, knownForResource, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForResource Context triple: [Grey Mountains, knownForResource, gold]
-
A.
targetResource
Indicates that one entity designates another entity as the specific resource or object toward which an action, request, or operation is directed.
-
B.
coveredResource
Indicates that one entity serves as a resource that is included within the scope or protection of another entity (such as a policy, agreement, or coverage).
-
C.
discoveredResource
chosen
Indicates that an entity has found, identified, or uncovered a particular resource.
-
D.
isResourceFor
Indicates that one entity serves as a resource, support, or means of use for another entity.
-
E.
basedOnResource
Indicates that one entity is derived from, created using, or conceptually dependent on another entity as its underlying resource.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.