Triple
T34397766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hal Lanier |
E882879
|
entity |
| Predicate | managedLevel |
P29724
|
FINISHED |
| Object | Major League Baseball |
—
|
NE NERFINISHED |
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: Major League Baseball | Statement: [Hal Lanier, managedLevel, Major League Baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedLevel Context triple: [Hal Lanier, managedLevel, Major League Baseball]
-
A.
levelManaged
Indicates that one entity is responsible for overseeing, controlling, or maintaining a particular level, degree, or tier associated with another entity.
-
B.
modificationLevel
Indicates the degree or extent to which something has been altered, adjusted, or changed from its original state.
-
C.
managedIn
chosen
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
D.
ordinationLevel
Indicates the hierarchical rank or degree of authority assigned to an entity within an ordered or structured system.
-
E.
managedTo
Indicates that an entity successfully accomplished or achieved a particular action or outcome, often despite difficulty or obstacles.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:59 a.m.