Triple
T21763320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-E3-LIN-2 |
E537215
|
entity |
| Predicate | modulus |
P144615
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Max-E3-LIN-2, modulus, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modulus Context triple: [Max-E3-LIN-2, modulus, 2]
-
A.
modulusType
Indicates the type or category of modulus associated with an entity or operation (e.g., which modulus definition or scheme is being used).
-
B.
secondCongruenceModulus
Indicates that the second argument specifies the modulus with respect to which two values are congruent in a modular arithmetic relationship.
-
C.
thirdCongruenceModulus
Indicates that the third argument serves as the modulus with respect to which two other quantities are congruent.
-
D.
firstCongruenceModulus
Indicates that the specified value is the modulus used in the first congruence of a system of modular equations or congruence relations.
-
E.
hasModuli
chosen
Indicates that an entity possesses or is characterized by one or more moduli (e.g., parameters, modulus values, or modular structures) relevant to its definition or behavior.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a711dc8190a786c9849dc344e8 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.