Triple
T27731345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SerializableAttribute |
E697436
|
entity |
| Predicate | isAttributeClass |
P163121
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [System.SerializableAttribute, isAttributeClass, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAttributeClass Context triple: [System.SerializableAttribute, isAttributeClass, true]
-
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.
isClassOf
Indicates that one entity is a class or category to which another entity belongs or is an instance of.
-
C.
hasClassName
Indicates that an entity is associated with or identified by a specific class name in a classification or type system.
-
D.
hasCharacterClass
Indicates that an entity (such as a character) belongs to or is assigned a particular character class or role type.
-
E.
holdsAttribute
Indicates that one entity possesses, exhibits, or is characterized by a particular attribute or property.
- 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_69f6369b658c8190bc6d697b9a4d5c03 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 3:11 p.m.