Triple
T33370995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dave Brundage |
E854489
|
entity |
| Predicate | levelManaged |
P176555
|
FINISHED |
| Object | minor leagues |
—
|
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: minor leagues | Statement: [Dave Brundage, levelManaged, minor leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelManaged Context triple: [Dave Brundage, levelManaged, minor leagues]
-
A.
levelServed
Indicates that a particular service, function, or resource is provided or made available at a specified level or tier.
-
B.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another entity.
-
C.
level3Label
Indicates the third-level category or sublabel assigned to an entity within a hierarchical labeling or classification system.
-
D.
levelWithinPME
Indicates that one entity’s level or degree is contained within, or falls under, the scope of another entity’s Project Management Environment (PME) level.
-
E.
metaLevel
Indicates a relationship where one entity operates at a higher, descriptive, or controlling level relative to another (e.g., a meta-level concept about an object-level concept).
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:35 a.m.