Triple
T553486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livadia Park |
E11891
|
entity |
| Predicate | hasPath |
P4374
|
FINISHED |
| Object | seaside promenade |
—
|
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: seaside promenade | Statement: [Livadia Park, hasPath, seaside promenade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPath Context triple: [Livadia Park, hasPath, seaside promenade]
-
A.
hasRoute
chosen
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
C.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
D.
hasVertex
Indicates that an object, typically a geometric shape or graph, includes a specified vertex as one of its corner or node points.
-
E.
hasPar
Indicates a relationship where one entity has another entity as its parent.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991b296481908cf27e1d1ec67052 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.