Triple
T18793038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirichlet characters |
E459563
|
entity |
| Predicate | valuesLieIn |
P93941
|
FINISHED |
| Object | roots of unity |
—
|
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: roots of unity | Statement: [Dirichlet characters, valuesLieIn, roots of unity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valuesLieIn Context triple: [Dirichlet characters, valuesLieIn, roots of unity]
-
A.
valuesIn
chosen
Indicates that one entity specifies or constrains the set of permissible values for another entity.
-
B.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
C.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
D.
satisfiesInequality
Indicates that one quantity or expression fulfills the condition specified by a given inequality relation (such as <, ≤, >, or ≥).
-
E.
positionInRange
Indicates that an entity’s position lies within a specified numerical or spatial range.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59787e5988190883ed575ab4b6dec |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.