Triple
T23518542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noboa family |
E574434
|
entity |
| Predicate | influencePeakPeriod |
P70162
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Noboa family, influencePeakPeriod, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencePeakPeriod Context triple: [Noboa family, influencePeakPeriod, late 20th century]
-
A.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
B.
activityPeakPeriod
chosen
Indicates the time period during which an activity reaches its highest level or intensity.
-
C.
namingPeakPeriod
Indicates that a specific time interval is designated or labeled as a peak period within a given context.
-
D.
typicalPeakDateRange
Indicates the usual calendar period during which the referenced phenomenon or activity most commonly reaches its highest intensity or occurrence.
-
E.
peakDays
Indicates the days on which something reaches its highest or most intense level of activity, usage, or occurrence.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa83c538819096bc548e3e0ddbd0 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.