Triple
T215361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fife Coastal Path |
E4807
|
entity |
| Predicate | suitableFor |
P98
|
FINISHED |
| Object | day walks |
—
|
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: day walks | Statement: [Fife Coastal Path, suitableFor, day walks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitableFor Context triple: [Fife Coastal Path, suitableFor, day walks]
-
A.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
C.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
D.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
E.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.