Triple

T7696522
Position Surface form Disambiguated ID Type / Status
Subject Hanunoo E174383 entity
Predicate timeOfUnicodeInclusion P27273 FINISHED
Object 2002 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: 2002 | Statement: [Hanunoo, timeOfUnicodeInclusion, 2002]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeOfUnicodeInclusion
Context triple: [Hanunoo, timeOfUnicodeInclusion, 2002]
  • A. timeOfCodification
    Indicates the specific point in time at which something (such as a rule, law, or concept) was formally codified or recorded.
  • B. UnicodeStandardVersionIntroduced
    Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
  • C. encodedInUnicodeSince chosen
    Indicates that a given character or symbol has been included and assigned a code point in the Unicode standard starting from a specific version or time.
  • D. hasUnicodeStandard
    Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
  • E. hasUnicodeStatus
    Indicates that a given entity has a particular Unicode-related classification or status (such as assigned, reserved, deprecated, or noncharacter) within the Unicode standard.
  • 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_69c6995a72cc8190998e56daa6f8e453 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c70402169481909b219dc5f4a64b9b completed March 27, 2026, 10:26 p.m.
PD Predicate disambiguation batch_69c70165e78c8190bf6b3c34e243cb81 completed March 27, 2026, 10:15 p.m.
Created at: March 27, 2026, 4:03 p.m.