Triple
T5680830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Resident Theatres |
E125193
|
entity |
| Predicate | hasAcronym |
P43
|
FINISHED |
| Object | LORT |
E367316
|
NE 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: LORT | Statement: [League of Resident Theatres, hasAcronym, LORT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LORT Context triple: [League of Resident Theatres, hasAcronym, LORT]
-
A.
LORT
chosen
LORT is the League of Resident Theatres, a major association of professional regional theaters in the United States that negotiates collective bargaining agreements and supports member institutions.
-
B.
Lour
Lour is a Scottish estate historically linked to the Carnegie family, notably associated with the title "Carnegie of Lour."
-
C.
LOP
LOP is the IATA airport code for Lombok International Airport, the main air gateway to the Indonesian island of Lombok.
-
D.
Loopt
Loopt was an early location-based social networking mobile app startup that allowed users to share their real-time location with friends.
-
E.
LOTG
LOTG is the standard abbreviation for the Laws of the Game, the official rulebook that governs how association football (soccer) is played worldwide.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02397c01081909793bb53ad7cbbce |
completed | March 22, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07dcb28888190affb0982060d5ea8 |
completed | March 22, 2026, 11:39 p.m. |
Created at: March 22, 2026, 3:44 p.m.