Triple
T35142476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ImprovOlympic |
E1014729
|
entity |
| Predicate | hasBranchInPast |
P73566
|
FINISHED |
| Object | Los Angeles |
—
|
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: Los Angeles | Statement: [ImprovOlympic, hasBranchInPast, Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchInPast Context triple: [ImprovOlympic, hasBranchInPast, Los Angeles]
-
A.
hasFormerBranchConnection
Indicates a relationship where two entities were previously connected through a branch affiliation that no longer exists.
-
B.
hasStateBranch
Indicates that one entity functions as a branch, subdivision, or local office of a larger parent entity within a particular state or regional jurisdiction.
-
C.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
D.
hadBranchIn
chosen
Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
-
E.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:02 p.m.