Triple
T11398735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | brachistochrone problem |
E270049
|
entity |
| Predicate | solutionCurve |
P27207
|
FINISHED |
| Object | cycloid |
—
|
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: cycloid | Statement: [brachistochrone problem, solutionCurve, cycloid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solutionCurve Context triple: [brachistochrone problem, solutionCurve, cycloid]
-
A.
relatedCurve
chosen
Indicates that one curve is associated with or derived from another curve in a defined relational way.
-
B.
curveEquation
Indicates that one entity is the mathematical equation that defines or represents the curve described by the other entity.
-
C.
curveEquationForm
Indicates that one entity is expressed as the mathematical equation or algebraic form that defines the shape or properties of a curve associated with another entity.
-
D.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
E.
commonlyUsedCurve
Indicates that the referenced curve is widely adopted or frequently used in common practice or standard applications.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001adc188190ae45227856156412 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.