Triple
T18479639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waring's problem |
E451523
|
entity |
| Predicate | knownValueOfG(k) |
P120529
|
FINISHED |
| Object | G(2) = 4 |
—
|
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: G(2) = 4 | Statement: [Waring's problem, knownValueOfG(k), G(2) = 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownValueOfG(k) Context triple: [Waring's problem, knownValueOfG(k), G(2) = 4]
-
A.
exactValueKnownFor
chosen
Indicates that the precise, specific value of something is known and established for an entity in a given context.
-
B.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
C.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
D.
hasKVNumber
Indicates that an entity is associated with a specific KV (kilovolt) identification number, typically used to label or reference electrical equipment or lines.
-
E.
learnsValueOf
Indicates that one entity acquires or comes to understand the value, meaning, or significance of another 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53065e8388190bb216dae89f8cf75 |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:35 a.m.