Triple
T36468798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mostow rigidity theorem |
E898487
|
entity |
| Predicate | typeOfRigidity |
P204014
|
FINISHED |
| Object | strong rigidity |
—
|
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: strong rigidity | Statement: [Mostow rigidity theorem, typeOfRigidity, strong rigidity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRigidity Context triple: [Mostow rigidity theorem, typeOfRigidity, strong rigidity]
-
A.
typeOfRig
Indicates the specific kind or configuration of rig used or associated with an entity.
-
B.
typeOfResistance
Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
-
C.
hardnessType
Indicates the specific category or classification of hardness associated with an entity.
-
D.
strainType
Indicates the specific variety or subtype classification within a broader category of strains (e.g., biological, chemical, or product strains).
-
E.
typeOfDensity
Indicates the specific category or kind of density (e.g., mass, population, charge) that characterizes a given quantity or measurement.
- F. None of above. chosen
Provenance (4 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a030c7d03308190a102689db1e8b657 |
completed | May 12, 2026, 11:18 a.m. |
| PD | Predicate disambiguation | batch_6a030a57b16c81909191270f64a77fcf |
completed | May 12, 2026, 11:09 a.m. |
| PDg | Predicate description generation | batch_6a030c7c58148190bf4bc76e6c5ee8f1 |
completed | May 12, 2026, 11:18 a.m. |
Created at: May 3, 2026, 4:10 p.m.