Triple
T20471045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermitian form |
E502192
|
entity |
| Predicate | homogeneityCondition |
P14261
|
FINISHED |
| Object | h(αx,y) = α h(x,y) |
—
|
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: h(αx,y) = α h(x,y) | Statement: [Hermitian form, homogeneityCondition, h(αx,y) = α h(x,y)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homogeneityCondition Context triple: [Hermitian form, homogeneityCondition, h(αx,y) = α h(x,y)]
-
A.
isHomogeneous
chosen
Indicates that all elements or parts involved share the same type, nature, or characteristics, without significant variation among them.
-
B.
requiresUniformity
Indicates that one entity imposes a condition that another entity (or set of entities) must be consistent or identical in a specified aspect.
-
C.
continuityCondition
Indicates that a relationship or process maintains consistency or unbroken progression across a boundary, interval, or sequence.
-
D.
equalityCondition
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
E.
uniquenessCondition
Indicates that a specified element, value, or combination of attributes must be unique within a given set, context, or domain, with no duplicates allowed.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e699608d7c8190910217817e789915 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.