Triple
T26900129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bachelorette |
E678002
|
entity |
| Predicate | typicalAgeRangeOfLead |
P199083
|
FINISHED |
| Object | mid-20s to mid-30s |
—
|
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: mid-20s to mid-30s | Statement: [The Bachelorette, typicalAgeRangeOfLead, mid-20s to mid-30s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgeRangeOfLead Context triple: [The Bachelorette, typicalAgeRangeOfLead, mid-20s to mid-30s]
-
A.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
B.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
C.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
D.
calledToLeadAtAge
Indicates that an entity was appointed or chosen to assume a leadership role when they were a specified age.
-
E.
focusesOnAgeRange
Indicates that something is specifically directed toward, concerned with, or tailored to a particular age range.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
| PDg | Predicate description generation | batch_69ff1e3d5f488190ba6e4f024128fb99 |
completed | May 9, 2026, 11:45 a.m. |
Created at: April 27, 2026, 5:50 a.m.