Triple

T3311901
Position Surface form Disambiguated ID Type / Status
Subject Stockport Viaduct E69590 entity
Predicate hasApproximateBrickCount P47203 FINISHED
Object over 11 million bricks 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: over 11 million bricks | Statement: [Stockport Viaduct, hasApproximateBrickCount, over 11 million bricks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateBrickCount
Context triple: [Stockport Viaduct, hasApproximateBrickCount, over 11 million bricks]
  • A. hasApproximateMemberCount
    Indicates that an entity is associated with a group or collection for which only an estimated or non-exact number of members is known.
  • B. hasApproximateLeaves
    Indicates that one entity possesses a number of leaves that is approximately equal to the number of leaves of another entity.
  • C. hasApproximateVendorCount
    Indicates that an entity is associated with an estimated or non-exact number of vendors.
  • D. hasApproximateNumberOfLetters
    Indicates that an entity is associated with a number that roughly, but not exactly, corresponds to the count of letters it contains.
  • E. approximateCapacity
    Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
  • 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_69ad85a0bb048190a5458d2738012d61 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb0eddf488190b7f05b3903b96d4b completed March 8, 2026, 5:25 p.m.
PD Predicate disambiguation batch_69ada4282730819092aa39c5f9269df0 completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69ada52716ec81908e89688a81039394 completed March 8, 2026, 4:34 p.m.
Created at: March 8, 2026, 3:11 p.m.