Triple

T595331
Position Surface form Disambiguated ID Type / Status
Subject Máximo the Titanosaur E17367 entity
Predicate visitorInteraction P5347 FINISHED
Object visitors can walk under parts of the skeleton 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: visitors can walk under parts of the skeleton | Statement: [Máximo the Titanosaur, visitorInteraction, visitors can walk under parts of the skeleton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: visitorInteraction
Context triple: [Máximo the Titanosaur, visitorInteraction, visitors can walk under parts of the skeleton]
  • A. visitorCenter
    Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
  • B. visitorCount
    Indicates the number of visitors associated with a particular entity, context, or time period.
  • C. interactionPoint chosen
    Indicates a specific location or moment where two or more entities come into contact or engage with each other.
  • D. hasInteraction
    Indicates that there is some form of interaction or mutual action occurring between the related entities.
  • E. visitorRequirement
    Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49bd280ac8190b6a530ce73da85c8 completed March 1, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69a494ceeb7881909a91ed1a35d5bf0a completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.