Triple
T20869660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The A Team |
E513855
|
entity |
| Predicate | liveDebutEvent |
P47969
|
FINISHED |
| Object | Crisis homeless charity gig |
—
|
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: Crisis homeless charity gig | Statement: [The A Team, liveDebutEvent, Crisis homeless charity gig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveDebutEvent Context triple: [The A Team, liveDebutEvent, Crisis homeless charity gig]
-
A.
liveDebutContext
Indicates the situational setting or circumstances under which a live debut event takes place.
-
B.
liveDebutApproxYear
Indicates the approximate calendar year in which an entity first made its live debut (e.g., first live performance or public appearance).
-
C.
liveDebutLocation
Indicates the location where an entity (such as an artist, performer, or work) is first presented or performed live.
-
D.
liveDebutYear
Indicates the year in which an entity first performed or appeared live (e.g., in concert, on stage, or in a live event).
-
E.
notableLivePerformanceEvent
chosen
Indicates that an entity is a significant or widely recognized live performance event associated with another entity (such as an artist, work, or venue).
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c4637ec48190830023d20fb8124c |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.