Triple

T14604761
Position Surface form Disambiguated ID Type / Status
Subject Australian honours system E342798 entity
Predicate recognisesField P115020 FINISHED
Object community service 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: community service | Statement: [Australian honours system, recognisesField, community service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognisesField
Context triple: [Australian honours system, recognisesField, community service]
  • A. supportsField
    Indicates that one entity provides the necessary structure, stability, or backing for a particular field, area, or domain associated with another entity.
  • B. definesField
    Indicates that one entity specifies or declares a particular field or attribute that belongs to or characterizes another entity.
  • C. coversField
    Indicates that one entity extends over, protects, or occupies the surface or area of a field associated with another entity.
  • D. isFixedFieldOf
    Indicates that one element is a fixed, non-variable field or attribute that belongs to and is structurally defined as part of another entity.
  • E. hasFieldName
    Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
  • F. None of above. chosen

Provenance (4 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_69d822dec68081908c2553145c4051dc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb44bf67c8190b4c48a7715f9443e completed April 14, 2026, 9:40 p.m.
PD Predicate disambiguation batch_69de656f9f4c81909f815b6629a9ee39 completed April 14, 2026, 4:03 p.m.
PDg Predicate description generation batch_69de716c17cc8190aeb85296abee85a7 completed April 14, 2026, 4:55 p.m.
Created at: April 10, 2026, 1:25 a.m.