Triple
T11961292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebesgue measure |
E284674
|
entity |
| Predicate | isRotationInvariant |
P4235
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lebesgue measure, isRotationInvariant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRotationInvariant Context triple: [Lebesgue measure, isRotationInvariant, true]
-
A.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
B.
hasCurvatureInvariant
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
-
C.
invariantUnder
chosen
Indicates that a property, structure, or quantity remains unchanged when a specified transformation or operation is applied.
-
D.
hasRotation
Indicates that one entity is rotated with respect to another, or possesses a specific rotational orientation or motion.
-
E.
hasRotationFrequency
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9036941948190b150369094551731 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.