Triple
T27133713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Souslin operation |
E681625
|
entity |
| Predicate | notablyGenerates |
P200380
|
FINISHED |
| Object | analytic sets |
—
|
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: analytic sets | Statement: [Souslin operation, notablyGenerates, analytic sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablyGenerates Context triple: [Souslin operation, notablyGenerates, analytic sets]
-
A.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notablyBorneBy
Indicates that something is especially or prominently carried, supported, or borne by a particular entity, in a way that is distinctive or noteworthy.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
notableRapid
Indicates a relationship where something is recognized as a particularly fast or unusually rapid instance or occurrence.
-
E.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
| PDg | Predicate description generation | batch_69ff878e8334819097e3c4bb5ca6ffa5 |
completed | May 9, 2026, 7:14 p.m. |
Created at: April 27, 2026, 9:05 a.m.