Triple
T18016848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | seaborn.set_context |
E431016
|
entity |
| Predicate | parameterType(rc) |
P125616
|
FINISHED |
| Object | dict or None |
—
|
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: dict or None | Statement: [seaborn.set_context, parameterType(rc), dict or None]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterType(rc) Context triple: [seaborn.set_context, parameterType(rc), dict or None]
-
A.
constructorParameterType
Indicates that a given parameter of a constructor has a specific data type.
-
B.
referenceType
Indicates the specific kind or category of reference relationship that one entity has to another.
-
C.
hasParameterType
chosen
Indicates that a parameter in a function, method, or operation is associated with a specific data type.
-
D.
representationType
Indicates the specific form or mode in which something is represented or expressed (e.g., as a symbol, image, model, or description).
-
E.
invocationType
Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9be5d0c819097e006f32d98753a |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.