Triple

T12535571
Position Surface form Disambiguated ID Type / Status
Subject The Round Mound of Rebound E299679 entity
Predicate hasBearerPrimaryNumber P105771 FINISHED
Object 34 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: 34 | Statement: [The Round Mound of Rebound, hasBearerPrimaryNumber, 34]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBearerPrimaryNumber
Context triple: [The Round Mound of Rebound, hasBearerPrimaryNumber, 34]
  • A. hasPrimaryBearer
    Indicates that one entity serves as the main or principal holder, carrier, or possessor of another entity.
  • B. hasNotableBearerOrdinalNumber
    Indicates that an entity is associated with a notable bearer identified by a specific ordinal position (e.g., first, second, third) among others with the same name or title.
  • C. firstBearer
    Indicates that the subject is the earliest or original entity to hold, possess, or carry the specified role, title, attribute, or item.
  • D. hasPrimaryNetwork
    Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
  • E. hasPrimary
    Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95f5507b481908d13cc317b7402f6 completed April 10, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69d9540d7b788190a0d57b098e90e491 completed April 10, 2026, 7:48 p.m.
PDg Predicate description generation batch_69d95f5148948190946a575d812b329d completed April 10, 2026, 8:36 p.m.
Created at: April 8, 2026, 9:57 p.m.