Triple
T27736742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyConfigurationAttribute |
E697546
|
entity |
| Predicate | targetUsage |
P2529
|
FINISHED |
| Object | assembly |
—
|
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: assembly | Statement: [System.Reflection.AssemblyConfigurationAttribute, targetUsage, assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUsage Context triple: [System.Reflection.AssemblyConfigurationAttribute, targetUsage, assembly]
-
A.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
usageCategory
Indicates the classification of how something is used or the type of usage it falls under.
-
E.
targetDistribution
Indicates the intended allocation or spread of something (such as resources, data, or outputs) across specified targets or recipients.
- 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 3:13 p.m.