Triple
T37441016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cayley surface |
E930419
|
entity |
| Predicate | isClassicalExampleOf |
P187820
|
FINISHED |
| Object | ruled cubic surface |
—
|
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: ruled cubic surface | Statement: [Cayley surface, isClassicalExampleOf, ruled cubic surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClassicalExampleOf Context triple: [Cayley surface, isClassicalExampleOf, ruled cubic surface]
-
A.
isCanonicalExampleOf
Indicates that something serves as a standard or typical instance that exemplifies a concept, category, or pattern.
-
B.
isHistoricExampleOf
Indicates that something serves as a notable past instance or case that exemplifies or illustrates a particular type, concept, or phenomenon.
-
C.
consideredClassic
Indicates that something is widely regarded or recognized as a classic within a particular field, genre, or context.
-
D.
isClassicalObjectIn
Indicates that a classical (non-quantum) object is located within or belongs to a specified region, context, or system.
-
E.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.