Triple

T17183564
Position Surface form Disambiguated ID Type / Status
Subject Lime House E417040 entity
Predicate hasDefinedBoundaries P126645 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: [Lime House, hasDefinedBoundaries, Yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDefinedBoundaries
Context triple: [Lime House, hasDefinedBoundaries, Yes]
  • A. hasIAUBoundariesDefinedBy
    Indicates that an entity’s boundaries are defined or delimited according to standards or specifications established by the International Astronomical Union (IAU).
  • B. hasBoundaryUnit
    Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
  • C. bordersDefinedIn
    Indicates that the boundaries or borders of one entity are specified, established, or formally described within another entity (such as a document, dataset, or legal instrument).
  • D. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • E. hasBoundaryShape
    Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
  • 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_69d886d5f34c8190b24564dfaa63f3fb completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42d9416a48190a5930fcd6008dbaa completed April 19, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69e383141ae0819096acd71683637cbc completed April 18, 2026, 1:11 p.m.
PDg Predicate description generation batch_69e39c2fedb881908bfed2c3e5f2616a completed April 18, 2026, 2:58 p.m.
Created at: April 10, 2026, 5:37 a.m.