Triple
T18956170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kummer surface |
E463785
|
entity |
| Predicate | PicardNumber |
P97266
|
FINISHED |
| Object | at least 17 |
—
|
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: at least 17 | Statement: [Kummer surface, PicardNumber, at least 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PicardNumber Context triple: [Kummer surface, PicardNumber, at least 17]
-
A.
hasPicardNumber
chosen
Indicates that an entity (typically an algebraic variety) has a specified Picard number, i.e., the rank of its Picard group.
-
B.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
-
C.
pillarNumber
Indicates the specific numerical identifier assigned to a particular pillar within a set or structure.
-
D.
numberInPreservation
Indicates that an entity has a specified quantity or count within a preservation context (such as items preserved, stored, or maintained).
-
E.
nationalTreasureNumber
Indicates that an entity is assigned a specific official national treasure identification number within a country’s heritage or cultural registry.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5cdf2d08190a0aecd3fa5335a75 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon