Triple
T30084965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juglar cycles |
E764577
|
entity |
| Predicate | typicalLengthUpperBoundYears |
P204255
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Juglar cycles, typicalLengthUpperBoundYears, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLengthUpperBoundYears Context triple: [Juglar cycles, typicalLengthUpperBoundYears, 11]
-
A.
typicalLengthLowerBoundYears
Indicates the minimum number of years that typically characterizes the length or duration of something.
-
B.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
-
C.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
D.
maximumAgeInYears
Indicates the highest allowable or observed age, expressed in years, associated with an entity or condition.
-
E.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0358c946f08190a8fb41c643074475 |
completed | May 12, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_6a03586e5bb08190a71e075fde7cd679 |
completed | May 12, 2026, 4:42 p.m. |
| PDg | Predicate description generation | batch_6a0358c89acc8190b22421ff8ce0f575 |
completed | May 12, 2026, 4:43 p.m. |
Created at: April 29, 2026, 7:04 p.m.