Triple
T9761634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSSet |
E236683
|
entity |
| Predicate | requiresEquatableElements |
P90872
|
FINISHED |
| Object | isEqual: |
—
|
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: isEqual: | Statement: [NSSet, requiresEquatableElements, isEqual:]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresEquatableElements Context triple: [NSSet, requiresEquatableElements, isEqual:]
-
A.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
B.
mayBeEqualTo
Indicates that two entities are possibly equal, but their equality is uncertain or not definitively established.
-
C.
isEquiconsistentWith
Indicates that two formal theories or systems have the same consistency strength, such that if one is consistent then the other is also consistent, and if one is inconsistent then so is the other.
-
D.
dimensionEquals
Indicates that two entities have exactly the same dimensional properties or measurements.
-
E.
hasComparableRank
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
- 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_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. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:25 p.m.