Triple
T22585005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode normalization |
E564765
|
entity |
| Predicate | definesForm |
P107129
|
FINISHED |
| Object | NFC |
—
|
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: NFC | Statement: [Unicode normalization, definesForm, NFC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesForm Context triple: [Unicode normalization, definesForm, NFC]
-
A.
describesForm
chosen
Indicates that one entity provides a description, specification, or characterization of the form or structure of another entity.
-
B.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
C.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
D.
weakFormDefinition
Indicates that one entity is the definition or specification of another entity expressed in a weak (e.g., variational, distributional, or generalized) mathematical form rather than in its strong or classical form.
-
E.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615c18f88190ad4f23639d15f337 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:45 p.m.