Triple
T6832814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauss’s remarkable theorem |
E157378
|
entity |
| Predicate | hasExampleApplication |
P54441
|
FINISHED |
| Object | proving that a cylinder is locally isometric to a 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: proving that a cylinder is locally isometric to a plane | Statement: [Gauss’s remarkable theorem, hasExampleApplication, proving that a cylinder is locally isometric to a plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExampleApplication Context triple: [Gauss’s remarkable theorem, hasExampleApplication, proving that a cylinder is locally isometric to a plane]
-
A.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
B.
exampleApplication
chosen
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
C.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
D.
hasNonExample
Indicates that something is associated with an instance that explicitly does not satisfy or illustrate a given concept, rule, or category.
-
E.
notableApplicationDevelopedOn
Indicates that a notable software application was created or built to run on a particular platform, system, or technology.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.