Triple
T17341067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banach limit |
E421066
|
entity |
| Predicate | normProperty |
P27187
|
FINISHED |
| Object | ‖L‖=1 |
—
|
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: ‖L‖=1 | Statement: [Banach limit, normProperty, ‖L‖=1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normProperty Context triple: [Banach limit, normProperty, ‖L‖=1]
-
A.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
B.
normType
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
C.
normDefinedBy
Indicates that a norm, rule, or standard is established, specified, or determined by a particular source or authority.
-
D.
normHierarchy
Indicates a hierarchical relationship between norms, where one norm is ranked as superior, more general, or otherwise governing in relation to another.
-
E.
normTakesValuesIn
chosen
Indicates that a norm or standard is defined such that its possible outcomes or assigned values lie within a specified set or range.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a15f6488190ad7d489e7391ab12 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.