Triple
T7420150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legendre symbol |
E171225
|
entity |
| Predicate | valueCondition |
P52973
|
FINISHED |
| Object | (a/p)=0 if p divides a |
—
|
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: (a/p)=0 if p divides a | Statement: [Legendre symbol, valueCondition, (a/p)=0 if p divides a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueCondition Context triple: [Legendre symbol, valueCondition, (a/p)=0 if p divides a]
-
A.
equalityCondition
chosen
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
B.
targetedCondition
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
C.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
D.
typeOfCondition
Indicates that one condition is a specific kind, category, or subtype of another condition.
-
E.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ea61248190886e8e55b42ba5f1 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.