Triple
T27734092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CaseInsensitiveComparer |
E697491
|
entity |
| Predicate | comparesType |
P149259
|
FINISHED |
| Object | System.String |
—
|
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.String | Statement: [CaseInsensitiveComparer, comparesType, System.String]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesType Context triple: [CaseInsensitiveComparer, comparesType, System.String]
-
A.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
B.
typeComparedAs
Indicates that two entities are being compared with respect to their types or classifications.
-
C.
matchesType
chosen
Indicates that one entity has the same or a compatible type as another entity according to a defined type system or classification.
-
D.
checkingType
Indicates that one entity is verifying, inspecting, or assessing the type or category of another entity.
-
E.
invariantComparisonType
Indicates the specific way in which two invariants are compared or evaluated relative to each 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_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 3:12 p.m.