Triple
T2348366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American League Rookie of the Year |
E45184
|
entity |
| Predicate | initialScope |
P13939
|
FINISHED |
| Object | entire Major 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: entire Major Leagues | Statement: [American League Rookie of the Year, initialScope, entire Major Leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialScope Context triple: [American League Rookie of the Year, initialScope, entire Major Leagues]
-
A.
scopeDefault
Indicates that something applies or is valid in the absence of a more specific or overriding scope.
-
B.
isGlobalScope
Indicates that something exists or applies at the global scope, rather than being limited to a local or nested context.
-
C.
scopeOfReset
Indicates the range or extent within which a reset action applies or takes effect.
-
D.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
locationScope
chosen
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.