Triple
T36932209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miquel circle |
E913508
|
entity |
| Predicate | theoremInvolves |
P49212
|
FINISHED |
| Object | Miquel theorem for quadrilaterals |
—
|
NE NERFINISHED |
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: Miquel theorem for quadrilaterals | Statement: [Miquel circle, theoremInvolves, Miquel theorem for quadrilaterals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theoremInvolves Context triple: [Miquel circle, theoremInvolves, Miquel theorem for quadrilaterals]
-
A.
hasTheorem
Indicates that one entity (typically a mathematical theory, field, or work) includes, establishes, or is associated with a particular theorem.
-
B.
relatedTheorem
chosen
Indicates that one theorem is connected to another through a logical, thematic, or derivational relationship.
-
C.
theoremStates
Indicates that a theorem formally asserts or expresses a particular statement, claim, or proposition.
-
D.
associatedConjecture
Indicates that one entity is linked or connected to a particular conjecture, typically as its subject, source, or relevant context.
-
E.
hasTheoremNamedAfter
Indicates that a theorem is named in honor of or after a particular person or entity.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.