Triple
T20627106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helly’s theorem |
E506847
|
entity |
| Predicate | isFiniteVersionOf |
P140825
|
FINISHED |
| Object | intersection properties of convex sets |
—
|
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: intersection properties of convex sets | Statement: [Helly’s theorem, isFiniteVersionOf, intersection properties of convex sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFiniteVersionOf Context triple: [Helly’s theorem, isFiniteVersionOf, intersection properties of convex sets]
-
A.
isGreaterVersionOf
Indicates that one version identifier represents a later or more advanced version than another.
-
B.
isInternalVersionOf
Indicates that one entity is an internal or non-public variant, edition, or build of another entity.
-
C.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
D.
definesVersionOf
Indicates that one entity specifies or establishes the version or variant identity of another entity.
-
E.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe576c081909231dc0d7304b9a9 |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.