Triple
T27731313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SerializableAttribute |
E697436
|
entity |
| Predicate | definedInAssembly |
P180704
|
FINISHED |
| Object | mscorlib |
—
|
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: mscorlib | Statement: [System.SerializableAttribute, definedInAssembly, mscorlib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedInAssembly Context triple: [System.SerializableAttribute, definedInAssembly, mscorlib]
-
A.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
B.
alsoDefinedInPackage
Indicates that the same element or concept is additionally defined or declared in another software package.
-
C.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
D.
definedInPart
Indicates that something is specified, described, or formally established within a particular part or section of a larger whole.
-
E.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
- F. None of above. chosen
Provenance (4 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 27, 2026, 3:11 p.m.