Triple
T32443899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langevin function |
E829089
|
entity |
| Predicate | inverseUsedIn |
P160524
|
FINISHED |
| Object | polymer chain elasticity models |
—
|
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: polymer chain elasticity models | Statement: [Langevin function, inverseUsedIn, polymer chain elasticity models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inverseUsedIn Context triple: [Langevin function, inverseUsedIn, polymer chain elasticity models]
-
A.
inverseUses
chosen
Indicates that one entity is used by another entity, expressing the inverse direction of a "uses" relationship.
-
B.
isInverseOf
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
inverseImage
Indicates the mapping from a set of outputs back to all inputs that are related to those outputs under a given function or relation.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e47f48819080d82e789fa9e3e7 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:55 a.m.