Triple
T22706310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rich Mountain |
E561460
|
entity |
| Predicate | timeInUseAsMine |
P2935
|
FINISHED |
| Object | from 16th century to present |
—
|
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: from 16th century to present | Statement: [Rich Mountain, timeInUseAsMine, from 16th century to present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInUseAsMine Context triple: [Rich Mountain, timeInUseAsMine, from 16th century to present]
-
A.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
B.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
C.
usedSince
chosen
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
D.
timePeriodTermUsedSince
Indicates that a particular time period term has been in use starting from a specified point in time.
-
E.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178ceba6c8190a538366a8e4648de |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.