Triple
T29938503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRG32k3a generator |
E760432
|
entity |
| Predicate | hasPeriodLength |
P188432
|
FINISHED |
| Object | approximately 2^191 |
—
|
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: approximately 2^191 | Statement: [MRG32k3a generator, hasPeriodLength, approximately 2^191]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodLength Context triple: [MRG32k3a generator, hasPeriodLength, approximately 2^191]
-
A.
hasAverageMonthLength
Indicates that an entity is associated with a specified average length of a month, typically expressed in days.
-
B.
hasWeekLength
Indicates the duration of a week associated with an entity, typically expressed as a number of days.
-
C.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
D.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
E.
hasTypicalBirthPeriod
Indicates the usual or characteristic time span during which the birth of an entity typically occurs.
- F. None of above. chosen
Provenance (4 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: April 29, 2026, 6:21 p.m.