Triple
T25891996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Mitchell Trail |
E652358
|
entity |
| Predicate | hasApproximateUsePeriod |
P97306
|
FINISHED |
| Object | modern era |
—
|
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: modern era | Statement: [Old Mitchell Trail, hasApproximateUsePeriod, modern era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateUsePeriod Context triple: [Old Mitchell Trail, hasApproximateUsePeriod, modern era]
-
A.
hasApproximateUse
Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another entity.
-
B.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
C.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
D.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
E.
availabilityPeriod
chosen
Indicates the time span during which something is available or valid for use.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 8:22 a.m.