Triple
T27731524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Runtime.Serialization.DataContractAttribute |
E697440
|
entity |
| Predicate | propertyType(Name) |
P166453
|
FINISHED |
| Object | System.String |
—
|
NE NERFINISHED |
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.String | Statement: [System.Runtime.Serialization.DataContractAttribute, propertyType(Name), System.String]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType(Name) Context triple: [System.Runtime.Serialization.DataContractAttribute, propertyType(Name), System.String]
-
A.
propertyType_id
Indicates a relationship that specifies the type or category of a property associated with an entity.
-
B.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
-
C.
propertyType_rid
Indicates that an entity is associated with a specific property type identified by a unique resource identifier (RID).
-
D.
propertyType_uri
Indicates that an entity has a specific type of property, identified by a URI.
-
E.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
- 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_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 27, 2026, 3:11 p.m.