Triple

T30396766
Position Surface form Disambiguated ID Type / Status
Subject $100,000 infield E773239 entity
Predicate hasMonetaryValueType P482 FINISHED
Object estimated combined market value of players 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: estimated combined market value of players | Statement: [$100,000 infield, hasMonetaryValueType, estimated combined market value of players]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMonetaryValueType
Context triple: [$100,000 infield, hasMonetaryValueType, estimated combined market value of players]
  • A. hasMonetaryComponent
    Indicates that something includes, involves, or is associated with a monetary or financial element.
  • B. monetaryValue chosen
    Indicates the amount of money associated with an entity, event, or transaction.
  • C. monetaryComponent
    Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
  • D. monetaryUnitOfAccount
    Indicates that something serves as the standard unit in which the value of goods, services, and financial transactions is measured and recorded.
  • E. monetaryStatus
    Indicates the financial condition or situation of an entity, such as its wealth, solvency, or level of monetary resources.
  • 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_69f2248facd48190b183c3f3ca6daef7 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fd4f39b5008190b83b3227ce22c509 completed May 8, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69fd4df17c548190a4e2a6fea70f7e10 completed May 8, 2026, 2:44 a.m.
Created at: April 29, 2026, 8:02 p.m.