Triple
T21086939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Basketball League (1925–1955) |
E519517
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | ABL |
—
|
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: ABL | Statement: [American Basketball League (1925–1955), alsoKnownAs, ABL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ABL Context triple: [American Basketball League (1925–1955), alsoKnownAs, ABL]
-
A.
ABL
ABL is the commonly used abbreviation for the Academia Brasileira de Letras, Brazil’s foremost literary and language academy.
-
B.
ABL
ABL is the IATA airport code assigned to Ambrolauri Airport in Georgia.
-
C.
ABL
chosen
ABL was a short-lived professional American basketball league that operated in the mid-1940s, preceding the formation of the NBA.
-
D.
ABL
ABL is the ICAO airline designator assigned to Air Busan, a South Korean low-cost carrier based in Busan.
-
E.
ABCL
ABCL (Armed Bear Common Lisp) is an implementation of the Common Lisp programming language that runs on the Java Virtual Machine, enabling interoperability with Java code.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094be9388190b004fda23f301397 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:50 p.m.