Triple
T27615844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET Base Class Library |
E700434
|
entity |
| Predicate | coreAssembly |
P98955
|
FINISHED |
| Object | System.dll |
—
|
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: System.dll | Statement: [.NET Base Class Library, coreAssembly, System.dll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreAssembly Context triple: [.NET Base Class Library, coreAssembly, System.dll]
-
A.
primaryAssembly
chosen
Indicates that one entity serves as the main or principal assembly to which another entity is structurally or organizationally related.
-
B.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
C.
coreConstruct
Indicates a fundamental building or organizing relationship where one entity serves as the essential basis or primary component from which another entity is formed or structured.
-
D.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
E.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:12 p.m.