Triple
T9761538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSObject |
E236681
|
entity |
| Predicate | superclassOf |
P62912
|
FINISHED |
| Object | NSProxy (indirectly via root semantics) |
—
|
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: NSProxy (indirectly via root semantics) | Statement: [NSObject, superclassOf, NSProxy (indirectly via root semantics)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superclassOf Context triple: [NSObject, superclassOf, NSProxy (indirectly via root semantics)]
-
A.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
B.
predecessorClass
Indicates that one class precedes another in an ordered sequence or hierarchy, typically representing an earlier version or prior stage of that class.
-
C.
typeOfAncestor
chosen
Indicates that one entity is an ancestor (of any generational distance) of another entity.
-
D.
isClassOf
Indicates that one entity is a class or category to which another entity belongs or is an instance of.
-
E.
successorClass
Indicates that one class directly follows or replaces another class in a sequence or hierarchy.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda04c70108190a8ed09eb6f2a124e |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.