Triple
T36469503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green’s conjecture |
E898503
|
entity |
| Predicate | openProblems |
P96492
|
FINISHED |
| Object | behavior in positive characteristic |
—
|
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: behavior in positive characteristic | Statement: [Green’s conjecture, openProblems, behavior in positive characteristic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openProblems Context triple: [Green’s conjecture, openProblems, behavior in positive characteristic]
-
A.
openProblemIn
chosen
Indicates that a particular problem or issue is currently active or unresolved within a specified context, domain, or environment.
-
B.
openProblemAsOf
Indicates that a problem or issue remains unsolved or unresolved as of a specified point in time.
-
C.
announcedMillenniumProblems
Indicates that an entity formally proclaimed or made public the set of Millennium Problems.
-
D.
numberOfProblems
Indicates the quantity or count of problems associated with a given entity or situation.
-
E.
problems
Indicates that one entity has issues, difficulties, or complications associated with or caused by 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.