Triple
T17569392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equatable |
E427894
|
entity |
| Predicate | designGuideline |
P81177
|
FINISHED |
| Object | equality must be reflexive symmetric and transitive |
—
|
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: equality must be reflexive symmetric and transitive | Statement: [Equatable, designGuideline, equality must be reflexive symmetric and transitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designGuideline Context triple: [Equatable, designGuideline, equality must be reflexive symmetric and transitive]
-
A.
designStandardizedIn
Indicates that something is designed according to the rules, formats, or specifications defined within a particular standard or standardization framework.
-
B.
designIssue
Indicates that there is a problem, flaw, or concern related to the design of an entity or system.
-
C.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
D.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
E.
hasGuideline
chosen
Indicates that one entity is governed, informed, or constrained by a rule, standard, or recommended procedure provided by another entity.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592fe8408190bd8fed1920ab3601 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.