Triple
T16892223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High-A Minor League Baseball |
E424201
|
entity |
| Predicate | ageRangeTypical |
P78532
|
FINISHED |
| Object | early-20s players |
—
|
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: early-20s players | Statement: [High-A Minor League Baseball, ageRangeTypical, early-20s players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRangeTypical Context triple: [High-A Minor League Baseball, ageRangeTypical, early-20s players]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
typicalAge
chosen
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
C.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
D.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
-
E.
typicalAgingPotentialRange
Indicates the usual range of time over which something is expected to age or mature 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc5a5308190937ebd05356bd91d |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.