Triple

T24253418
Position Surface form Disambiguated ID Type / Status
Subject Unicode Standard Annex #38 E603596 entity
Predicate hasSection P35 FINISHED
Object Informative Properties
Informative Properties is a section of Unicode Standard Annex #38 that documents non-normative, supplemental character information useful for text processing and analysis.
E1624911 NE 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: Informative Properties | Statement: [Unicode Standard Annex #38, hasSection, Informative Properties]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Informative Properties
Triple: [Unicode Standard Annex #38, hasSection, Informative Properties]
Generated description
Informative Properties is a section of Unicode Standard Annex #38 that documents non-normative, supplemental character information useful for text processing and analysis.

Provenance (5 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_69e29540da0481909a38bdae315b7a02 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28b8bcb1c8190995e464a5f85fba9 completed April 29, 2026, 10:51 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fbd39b8b881909a8623093e0464c0 completed May 22, 2026, 2:19 a.m.
NEDg Description generation batch_6a0fbf90cb488190acfdf236e2b28338 completed May 22, 2026, 2:29 a.m.
NED2 Entity disambiguation (via description) batch_6a0fc06a9f2481909c0e770b96664781 completed May 22, 2026, 2:33 a.m.
Created at: April 18, 2026, 12:05 a.m.