Triple
T28864445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyke Wake Walk |
E728958
|
entity |
| Predicate | waymarkStatus |
P142396
|
FINISHED |
| Object | partly waymarked |
—
|
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: partly waymarked | Statement: [Lyke Wake Walk, waymarkStatus, partly waymarked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waymarkStatus Context triple: [Lyke Wake Walk, waymarkStatus, partly waymarked]
-
A.
waymarkingStatus
chosen
Indicates the current state or condition of a waymarking process, such as whether a location or route has been identified, recorded, approved, or otherwise classified in a waymarking system.
-
B.
monumentStatus
Indicates the official designation or condition of an entity as a monument, such as whether it is recognized, protected, or classified under heritage or preservation status.
-
C.
visitorAttractionStatus
Indicates the current operational or accessibility status of a visitor attraction (e.g., open, closed, restricted).
-
D.
notableStructureStatus
Indicates the status or condition of a structure that is considered notable or significant.
-
E.
marksStatus
Indicates that one entity assigns, records, or updates the status or condition of 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a1a21ac819084b6b38b871d9759 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:48 a.m.