Triple
T32385387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 小篆 |
E827531
|
entity |
| Predicate | 文字规范作用 |
P33765
|
FINISHED |
| Object | 统一秦境内各地异体字 |
—
|
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: 统一秦境内各地异体字 | Statement: [小篆, 文字规范作用, 统一秦境内各地异体字]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 文字规范作用 Context triple: [小篆, 文字规范作用, 统一秦境内各地异体字]
-
A.
languageStandardizationRole
chosen
Indicates the role an entity plays in establishing, maintaining, or influencing the standardization of a language.
-
B.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
C.
languageReform
Indicates efforts or actions aimed at changing, standardizing, or improving aspects of a language, such as its spelling, grammar, or usage rules.
-
D.
regulatesOrStandardizes
Indicates that one entity establishes, enforces, or defines rules, norms, or standards that govern the behavior, quality, or operation of another entity.
-
E.
hasOrthographyGuidelinesBy
Indicates that an entity’s orthography (writing system or spelling conventions) is defined, regulated, or guided by 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1cf2aa081909f4c0b8f0cad1907 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.