Triple
T26925860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aryabhatiya |
E677775
|
entity |
| Predicate | approximateValueOfPi |
P4460
|
FINISHED |
| Object | 3.1416 |
—
|
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: 3.1416 | Statement: [Aryabhatiya, approximateValueOfPi, 3.1416]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateValueOfPi Context triple: [Aryabhatiya, approximateValueOfPi, 3.1416]
-
A.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
B.
approximates
chosen
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
alignedApproximately
Indicates that two or more entities are positioned or oriented in roughly the same direction or arrangement, allowing for minor deviations or imprecision.
-
D.
approximateSquare
Indicates that one quantity is approximately equal to the square of another quantity, within some acceptable margin of error.
-
E.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 6:09 a.m.