Triple

T12313092
Position Surface form Disambiguated ID Type / Status
Subject Jaguariúna E293529 entity
Predicate hasSectorPolicy P7262 FINISHED
Object agribusiness development 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: agribusiness development | Statement: [Jaguariúna, hasSectorPolicy, agribusiness development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSectorPolicy
Context triple: [Jaguariúna, hasSectorPolicy, agribusiness development]
  • A. hasPolicySupport
    Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
  • B. hasPolicyStatus
    Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
  • C. hasEnrollmentPolicy
    Indicates that there is a specific rule or set of rules governing who may enroll in, access, or participate in something and under what conditions.
  • D. hasPolicyArea chosen
    Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
  • E. hasReferencePolicy
    Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
  • 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_69d6ab6a2b50819082f6aedd32ed608a completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f621570819091ee1db2609233ea completed April 10, 2026, 6:20 p.m.
PD Predicate disambiguation batch_69d93ec02c008190a56aae60a3d9eff6 completed April 10, 2026, 6:17 p.m.
Created at: April 8, 2026, 9:53 p.m.