Triple
T4021212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNIP |
E91282
|
entity |
| Predicate | fieldNormalizationMethod |
P12712
|
FINISHED |
| Object | source-normalization |
—
|
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: source-normalization | Statement: [SNIP, fieldNormalizationMethod, source-normalization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldNormalizationMethod Context triple: [SNIP, fieldNormalizationMethod, source-normalization]
-
A.
usesNormalization
Indicates that one entity applies or relies on a normalization process or technique in relation to another entity or data.
-
B.
normalizationAttempt
Indicates an effort to convert something into a standard or consistent form according to defined rules or criteria.
-
C.
normType
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
D.
standardizationApproach
chosen
Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
-
E.
weightingMethod
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.