Triple
T2648700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL East |
E53844
|
entity |
| Predicate | hasLevelBelow |
P32836
|
FINISHED |
| Object | Minor League Baseball affiliates of member clubs |
—
|
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 League Baseball affiliates of member clubs | Statement: [NL East, hasLevelBelow, Minor League Baseball affiliates of member clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelBelow Context triple: [NL East, hasLevelBelow, Minor League Baseball affiliates of member clubs]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
hasLowerTier
chosen
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
C.
hasLowerLevelLine
Indicates that one line is positioned or ranked below another line within a hierarchical or layered structure.
-
D.
hasClearanceBelow
Indicates that one entity’s clearance level is lower than another entity’s clearance level.
-
E.
membershipLevelBelow
Indicates that one entity’s membership level is ranked lower or less privileged than another entity’s membership level.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91b4b3c81908571e85a1621dfc5 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.