Triple
T12597324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stirling's approximation |
E300765
|
entity |
| Predicate | hasLeadingFactor |
P63069
|
FINISHED |
| Object | √(2πn) |
—
|
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: √(2πn) | Statement: [Stirling's approximation, hasLeadingFactor, √(2πn)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadingFactor Context triple: [Stirling's approximation, hasLeadingFactor, √(2πn)]
-
A.
hasDenominatorFactor
Indicates that one value appears as a factor in the denominator of another value or expression.
-
B.
requiresLeadingIn
Indicates that one entity must be introduced, prepared, or preceded by another entity or action before it can appropriately occur or be used.
-
C.
hasStepsLeadingTo
Indicates that one location or object is connected to another by a set of steps or a staircase leading toward it.
-
D.
isLeadingIn
Indicates that one entity is currently ahead of or outperforming another in a specified context, such as a competition, ranking, or metric.
-
E.
givesLeadingTerm
chosen
Indicates that one entity provides or specifies the leading term (typically the highest-order or most significant term) of another entity, such as a polynomial or expression.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.