Triple
T31943909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfenstein parameterization |
E815595
|
entity |
| Predicate | expansionIn |
P8787
|
FINISHED |
| Object | small parameter λ |
—
|
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: small parameter λ | Statement: [Wolfenstein parameterization, expansionIn, small parameter λ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionIn Context triple: [Wolfenstein parameterization, expansionIn, small parameter λ]
-
A.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
B.
expandsIn
chosen
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
C.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
D.
expansionOrContraction
Indicates a change in size, volume, or extent of something, whether it is increasing (expanding) or decreasing (contracting).
-
E.
expansionFrom
Indicates that one entity results from or is derived through the enlargement, extension, or unfolding of 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 12:06 a.m.