Triple
T25433158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liouville number |
E637310
|
entity |
| Predicate | disjointFrom |
P23696
|
FINISHED |
| Object | algebraic numbers |
—
|
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: algebraic numbers | Statement: [Liouville number, disjointFrom, algebraic numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disjointFrom Context triple: [Liouville number, disjointFrom, algebraic numbers]
-
A.
areDisjointWith
chosen
Indicates that two entities have no elements, instances, or members in common within the specified context.
-
B.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
C.
notCoterminousWith
Indicates that two entities do not share the same boundaries in space, time, or extent and therefore are not exactly coincident.
-
D.
complementOf
Indicates that one entity serves as a complement to another, completing or specifying it in a grammatical or semantic relationship.
-
E.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dc7d088190b1e4c191172ea256 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:58 p.m.