Triple
T19465814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas League |
E486993
|
entity |
| Predicate | typicalPlayerLevel |
P90637
|
FINISHED |
| Object | upper-level minor league prospects |
—
|
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: upper-level minor league prospects | Statement: [Texas League, typicalPlayerLevel, upper-level minor league prospects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlayerLevel Context triple: [Texas League, typicalPlayerLevel, upper-level minor league prospects]
-
A.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
B.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
C.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
D.
typicalLowestLevel
Indicates that something represents the most basic or minimal level that is commonly or normally found within a given context.
-
E.
typicalExperienceLevel
chosen
Indicates the usual or most common level of experience associated with an entity in a given context.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e1dccc819096feb1a514b9eb86 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.