Triple
T493008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Recreation Trail |
E10228
|
entity |
| Predicate | hasDesignationSign |
P9766
|
FINISHED |
| Object | National Recreation Trail emblem |
—
|
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: National Recreation Trail emblem | Statement: [National Recreation Trail, hasDesignationSign, National Recreation Trail emblem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignationSign Context triple: [National Recreation Trail, hasDesignationSign, National Recreation Trail emblem]
-
A.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
hasLetterDesignation
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
C.
hasSign
chosen
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
D.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
E.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0faab4881909f65f172198b5bd2 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.