Triple
T6203183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiel Fellowship |
E138684
|
entity |
| Predicate | typicalAgeRangeOfFellows |
P2736
|
FINISHED |
| Object | late teens to early twenties |
—
|
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 teens to early twenties | Statement: [Thiel Fellowship, typicalAgeRangeOfFellows, late teens to early twenties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgeRangeOfFellows Context triple: [Thiel Fellowship, typicalAgeRangeOfFellows, late teens to early twenties]
-
A.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
B.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
typicalAgeAtSelection
Indicates the usual or most common age at which an entity is chosen or selected for a particular role, status, or process.
-
D.
typicalAgeAtCompletion
Indicates the age at which an entity (such as a program, activity, or process) is typically completed.
-
E.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626a32908190a3332008aee2e4a9 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.