Triple
T11918942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitting subgroup |
E283603
|
entity |
| Predicate | isNormalIn |
P102340
|
FINISHED |
| Object | G |
—
|
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: G | Statement: [Fitting subgroup, isNormalIn, G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNormalIn Context triple: [Fitting subgroup, isNormalIn, G]
-
A.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
B.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
C.
areRegularIn
Indicates that entities participate in or occur within a context, pattern, or structure in a consistent, uniform, and rule-governed manner.
-
D.
conditionForNorm
Indicates that a certain condition or set of conditions must hold for a particular norm, rule, or obligation to be applicable or in force.
-
E.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
- F. None of above. chosen
Provenance (4 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.