Triple
T19274882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort to Sea Trail |
E482022
|
entity |
| Predicate | isSignedRoute |
P135399
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fort to Sea Trail, isSignedRoute, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignedRoute Context triple: [Fort to Sea Trail, isSignedRoute, yes]
-
A.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
B.
isSignedAlong
Indicates that an entity has signed or endorsed something in conjunction with another specified entity.
-
C.
mayBeSignedAs
Indicates that one entity can optionally be used or recognized as the signature or signed form of another entity.
-
D.
typicallySignedWith
Indicates that an entity is most commonly or customarily accompanied by a particular signature, mark, or signing method.
-
E.
requiresSignatureOf
Indicates that one entity must obtain or depend on the formal signature or signed approval of another entity.
- F. None of above. chosen
Provenance (4 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbb2fc08190b417a6d0b7a9d6b8 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.