Triple
T27733088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IComparable |
E697474
|
entity |
| Predicate | CompareToReturnType |
P91196
|
FINISHED |
| Object | System.Int32 |
—
|
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.Int32 | Statement: [System.IComparable, CompareToReturnType, System.Int32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CompareToReturnType Context triple: [System.IComparable, CompareToReturnType, System.Int32]
-
A.
comparisonMethod
Indicates the method or criteria used to compare two or more entities or values.
-
B.
invariantComparisonType
Indicates the specific way in which two invariants are compared or evaluated relative to each other.
-
C.
isComparisonSort
Indicates that the sorting algorithm operates by comparing pairs of elements to determine their order.
-
D.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
E.
comparisonResult
chosen
Indicates the outcome of comparing two entities, typically expressing whether one is less than, equal to, or greater than the other.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 3:12 p.m.