Triple
T22291055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Nationals farm system |
E550995
|
entity |
| Predicate | levelIncluded |
P29174
|
FINISHED |
| Object | Triple-A |
—
|
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: Triple-A | Statement: [Washington Nationals farm system, levelIncluded, Triple-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelIncluded Context triple: [Washington Nationals farm system, levelIncluded, Triple-A]
-
A.
exportLevel
Indicates the degree or extent to which something is produced in one place and sent out or made available to other places or markets.
-
B.
levelServed
Indicates that a particular service, function, or resource is provided or made available at a specified level or tier.
-
C.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another entity.
-
D.
coversLevel
chosen
Indicates that one entity includes or encompasses a particular level or layer of another entity or system.
-
E.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560c47e481908b33de63a11e25de |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.