Triple
T6082942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1777 Trail |
E135566
|
entity |
| Predicate | hasModernUseSince |
P46987
|
FINISHED |
| Object | 20th century (as a recreational trail) |
—
|
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: 20th century (as a recreational trail) | Statement: [1777 Trail, hasModernUseSince, 20th century (as a recreational trail)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernUseSince Context triple: [1777 Trail, hasModernUseSince, 20th century (as a recreational trail)]
-
A.
hasModernSiteUse
Indicates that an entity is currently used or functions in a particular way at a modern site or location.
-
B.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
C.
hasModernFormulationIn
Indicates that something has a contemporary or updated version expressed or formulated within a specified context, framework, or medium.
-
D.
modernUse
Indicates how something is currently used or applied in modern times.
-
E.
areUsedSince
chosen
Indicates that entities have been in use continuously starting from a specified point in time.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05786233c81909010a6c2f7e7dfda |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.