Triple
T29565926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artin conductor |
E753160
|
entity |
| Predicate | parameterOf |
P12016
|
FINISHED |
| Object | Artin L-function |
—
|
NE NERFINISHED |
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: Artin L-function | Statement: [Artin conductor, parameterOf, Artin L-function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterOf Context triple: [Artin conductor, parameterOf, Artin L-function]
-
A.
parameter
chosen
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
parametrizes
Indicates that one entity defines or controls the variable parameters that determine the behavior, form, or configuration of another entity.
-
C.
parameterLivesIn
Indicates that a given parameter or variable is associated with, resides within, or is scoped to a particular context, environment, or container.
-
D.
genericParameter
Indicates that one entity functions as a type or template parameter that is supplied to or constrained by another entity.
-
E.
parameterSet
Indicates that one entity is a collection or configuration of parameters associated with or applied to another entity.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 5:52 p.m.