Triple
T565392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Way (Delphi) |
E13540
|
entity |
| Predicate | linedWith |
P10266
|
FINISHED |
| Object | treasuries |
—
|
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: treasuries | Statement: [Sacred Way (Delphi), linedWith, treasuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linedWith Context triple: [Sacred Way (Delphi), linedWith, treasuries]
-
A.
isLinedWith
chosen
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
B.
stricken
Indicates that an entity has been severely affected, harmed, or afflicted by something (such as illness, disaster, or misfortune).
-
C.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
D.
mantlingLined
Indicates that the inner surface of a heraldic mantling is lined with a specified material, color, or pattern.
-
E.
lineUses
Indicates that a particular line (such as a route, service, or connection) makes use of or is implemented using a specified resource, infrastructure, or element.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a74793481908fee3baff0b1d348 |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.