Triple

T4304886
Position Surface form Disambiguated ID Type / Status
Subject Virgin Valley E99929 entity
Predicate allowsFeeDigging P273 FINISHED
Object true 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: true | Statement: [Virgin Valley, allowsFeeDigging, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsFeeDigging
Context triple: [Virgin Valley, allowsFeeDigging, true]
  • A. allowsRedemptionFor
    Indicates that one party grants another the right or ability to redeem something (such as a benefit, asset, or offer) under specified conditions.
  • B. canElect
    Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
  • C. allows chosen
    Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
  • D. isPermissionless
    Indicates that an action, process, or system can be accessed or participated in by anyone without requiring prior approval or authorization from a central authority.
  • E. canConcurIn
    Indicates that one entity is able or permitted to agree with, coincide with, or participate jointly in the same event, decision, or condition as another entity.
  • 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_69b345528ebc8190b5abc7e95094792d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b350b8e1cc819094ce3d6f6c8da767 completed March 12, 2026, 11:48 p.m.
PD Predicate disambiguation batch_69b347ff45cc8190b0cc335a94cc3d73 completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:09 p.m.