Triple
T27736730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyDescriptionAttribute |
E697545
|
entity |
| Predicate | metadataRole |
P108488
|
FINISHED |
| Object | descriptive |
—
|
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: descriptive | Statement: [System.Reflection.AssemblyDescriptionAttribute, metadataRole, descriptive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataRole Context triple: [System.Reflection.AssemblyDescriptionAttribute, metadataRole, descriptive]
-
A.
roleInMetadata
chosen
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
B.
declaredRoleOfAuthor
Indicates that a specific role or capacity has been explicitly stated or assigned to an author in relation to a work or contribution.
-
C.
managementRole
Indicates that one entity holds a managerial or supervisory role with authority and responsibility over another entity.
-
D.
conceptualRole
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
E.
massRole
Indicates that an entity plays a specific role or function within a mass or collective context.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:13 p.m.