Triple
T27731320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SerializableAttribute |
E697436
|
entity |
| Predicate | hasAttributeUsage |
P163524
|
FINISHED |
| Object | AttributeTargets.Class |
—
|
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: AttributeTargets.Class | Statement: [System.SerializableAttribute, hasAttributeUsage, AttributeTargets.Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttributeUsage Context triple: [System.SerializableAttribute, hasAttributeUsage, AttributeTargets.Class]
-
A.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
B.
hasVariantUsage
Indicates that an entity is used in an alternative or non-standard way compared to its primary or canonical usage.
-
C.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
D.
holdsAttribute
Indicates that one entity possesses, exhibits, or is characterized by a particular attribute or property.
-
E.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
- 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_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 3:11 p.m.