Triple
T18051073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dataclasses |
E431926
|
entity |
| Predicate | classConfigurationParameter |
P28533
|
FINISHED |
| Object | init |
—
|
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: init | Statement: [dataclasses, classConfigurationParameter, init]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classConfigurationParameter Context triple: [dataclasses, classConfigurationParameter, init]
-
A.
configurationName
Indicates the specific label or identifier assigned to a particular configuration setting or setup.
-
B.
configurationOptionIn
chosen
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
-
C.
compositionParameter
Indicates that one entity serves as a parameter or component used in defining, configuring, or constructing the composition of another entity.
-
D.
configurableProperty
Indicates that an entity has a setting or attribute whose value can be adjusted or customized, typically to modify its behavior or characteristics.
-
E.
constructorParameterType
Indicates that a given parameter of a constructor has a specific data type.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff57ea08190a30a87993f7d3299 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.