Triple

T32263229
Position Surface form Disambiguated ID Type / Status
Subject Max-D E824215 entity
Predicate hasFanReputation P144861 FINISHED
Object one of the most intense Monster Jam trucks 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: one of the most intense Monster Jam trucks | Statement: [Max-D, hasFanReputation, one of the most intense Monster Jam trucks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFanReputation
Context triple: [Max-D, hasFanReputation, one of the most intense Monster Jam trucks]
  • A. haveReputation
    Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
  • B. fanExperienceReputation chosen
    Indicates the perceived quality or reputation of the experience that fans have with a person, organization, or event.
  • C. hasReputationAmong
    Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
  • D. hasViewReputation
    Indicates that an entity holds a reputation or recognized standing specifically related to viewing, observing, or accessing something.
  • E. hasQuirkyReputation
    Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
  • 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_69f3490e73588190915f282edd105772 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fd35d108908190b79b1e8e6bbd62aa completed May 8, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69fd34cb46108190b43c3b7f67ec4cd4 completed May 8, 2026, 12:56 a.m.
Created at: May 1, 2026, 12:42 a.m.