Triple
T33578646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seiberg–Witten differential |
E860093
|
entity |
| Predicate | hasAnalyticProperty |
P23698
|
FINISHED |
| Object | meromorphic |
—
|
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: meromorphic | Statement: [Seiberg–Witten differential, hasAnalyticProperty, meromorphic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnalyticProperty Context triple: [Seiberg–Witten differential, hasAnalyticProperty, meromorphic]
-
A.
hasAnalyticUse
Indicates that something is used for analysis, examination, or systematic study of another thing or situation.
-
B.
isAnalyticOn
Indicates that a function is analytic (holomorphic) throughout a specified domain or region.
-
C.
hasAnalyticGrammar
Indicates that an entity possesses or is characterized by an analytic grammar, where grammatical relationships are expressed primarily through separate words rather than inflection.
-
D.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
E.
hasAnalysisType
Indicates that one entity is associated with, or characterized by, a specific type or category of analysis applied to it.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:40 a.m.