Triple
T27731527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Runtime.Serialization.DataContractAttribute |
E697440
|
entity |
| Predicate | propertyType(IsNameSetExplicitly) |
P166453
|
FINISHED |
| Object | System.Boolean |
—
|
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: System.Boolean | Statement: [System.Runtime.Serialization.DataContractAttribute, propertyType(IsNameSetExplicitly), System.Boolean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType(IsNameSetExplicitly) Context triple: [System.Runtime.Serialization.DataContractAttribute, propertyType(IsNameSetExplicitly), System.Boolean]
-
A.
propertyType(Name)
chosen
Indicates that an entity has a specific type or category of property identified by Name.
-
B.
propertyType(Namespace)
Indicates that a given entity is classified as a specific type of property within the referenced namespace.
-
C.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
-
D.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
E.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
- 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_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 3:11 p.m.