Triple
T32378106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SqlDataAdapter |
E827341
|
entity |
| Predicate | constructorOverload |
P66397
|
FINISHED |
| Object | SqlDataAdapter() |
—
|
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: SqlDataAdapter() | Statement: [SqlDataAdapter, constructorOverload, SqlDataAdapter()]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorOverload Context triple: [SqlDataAdapter, constructorOverload, SqlDataAdapter()]
-
A.
constructorAccepts
Indicates that a constructor takes a specified parameter or set of parameters as part of its definition.
-
B.
hasOverload
chosen
Indicates that an entity defines multiple variants (overloads) of the same operation or function, typically distinguished by differing parameters or signatures.
-
C.
usesConstructor
Indicates that one entity creates or initializes another entity by invoking its constructor.
-
D.
hasConstructor
Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
-
E.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 12:51 a.m.