Triple
T10991910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montel's theorem |
E259771
|
entity |
| Predicate | domainType |
P24492
|
FINISHED |
| Object | open subset of the complex plane |
—
|
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: open subset of the complex plane | Statement: [Montel's theorem, domainType, open subset of the complex plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainType Context triple: [Montel's theorem, domainType, open subset of the complex plane]
-
A.
typicalDomain
chosen
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
B.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
C.
partOfDomain
Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
-
D.
domainServed
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
E.
domainCharacteristic
Indicates that a domain or area of interest possesses a particular characteristic or defining property.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d1e918819090c71f5a077fa15a |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.