Triple
T17607969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Morgan's laws |
E428884
|
entity |
| Predicate | hasSetForm |
P128259
|
FINISHED |
| Object | (A ∩ B)^c = A^c ∪ B^c |
—
|
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: (A ∩ B)^c = A^c ∪ B^c | Statement: [De Morgan's laws, hasSetForm, (A ∩ B)^c = A^c ∪ B^c]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetForm Context triple: [De Morgan's laws, hasSetForm, (A ∩ B)^c = A^c ∪ B^c]
-
A.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
hasSettlementForm
Indicates that an entity is associated with, or characterized by, a particular type or form of settlement (e.g., village, town, city).
-
C.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
-
D.
hasFormFor
Indicates that one entity possesses or provides a specific form or document intended to be used by another entity or for a particular purpose.
-
E.
hasMaterialFormOnSet
Indicates that something possesses a tangible, physical form or embodiment during the production or staging of a set.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4d8374819097cb112fba405e77 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:51 a.m.