Triple
T36469096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koebe function |
E898494
|
entity |
| Predicate | hasSlitType |
P185550
|
FINISHED |
| Object | slit along the negative real axis |
—
|
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: slit along the negative real axis | Statement: [Koebe function, hasSlitType, slit along the negative real axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSlitType Context triple: [Koebe function, hasSlitType, slit along the negative real axis]
-
A.
hasSlab
Indicates that one entity possesses, includes, or is associated with a slab component or slab-like element.
-
B.
hasSpitType
Indicates that one entity possesses or is characterized by a particular type or category of spit.
-
C.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
D.
slipType
Indicates the specific category or kind of slip involved in an action or relationship between entities.
-
E.
hasTypicalCut
Indicates that one entity is characterized by or associated with a standard or typical type of cut of another entity.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.