Triple
T27736639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyVersionAttribute |
E697543
|
entity |
| Predicate | typicalUsageLocation |
P21833
|
FINISHED |
| Object | AssemblyInfo.cs |
—
|
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: AssemblyInfo.cs | Statement: [System.Reflection.AssemblyVersionAttribute, typicalUsageLocation, AssemblyInfo.cs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUsageLocation Context triple: [System.Reflection.AssemblyVersionAttribute, typicalUsageLocation, AssemblyInfo.cs]
-
A.
typicalUseLocation
chosen
Indicates the usual or most common location where an entity is used or operates.
-
B.
hasTypicalUsageRegion
Indicates that something is most commonly or characteristically used within a particular geographic region.
-
C.
typicalSectorUse
Indicates the type of sector in which something is most commonly or characteristically used.
-
D.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
-
E.
typicalLocationOnProduct
Indicates the usual physical place or area on a product where something (e.g., a feature, label, or component) is commonly found.
- 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_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: April 27, 2026, 3:13 p.m.