Triple
T16605629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian mathematics |
E403440
|
entity |
| Predicate | typicalProblemType |
P115995
|
FINISHED |
| Object | bread and beer distribution problems |
—
|
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: bread and beer distribution problems | Statement: [Egyptian mathematics, typicalProblemType, bread and beer distribution problems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProblemType Context triple: [Egyptian mathematics, typicalProblemType, bread and beer distribution problems]
-
A.
typicalProblem
chosen
Indicates that a situation, issue, or obstacle is representative or characteristic of the usual problems encountered in a given context.
-
B.
problemType
Indicates the specific category or classification of a problem within a defined problem space or system.
-
C.
problemTypeSolved
Indicates that a given problem has been successfully solved or resolved by a particular entity or method.
-
D.
problemStatement
Indicates that an entity presents, defines, or expresses a specific problem or issue to be addressed.
-
E.
typicalQuestion
Indicates that an entity is a common or standard question typically asked in a given context or situation.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36090cf388190b401c55230912104 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.