Triple
T263451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fireside chats on banking crisis |
E5801
|
entity |
| Predicate | hasTitleOfFirstTalk |
P3254
|
FINISHED |
| Object | On the Bank Crisis |
—
|
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: On the Bank Crisis | Statement: [Fireside chats on banking crisis, hasTitleOfFirstTalk, On the Bank Crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleOfFirstTalk Context triple: [Fireside chats on banking crisis, hasTitleOfFirstTalk, On the Bank Crisis]
-
A.
containsTitle
chosen
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
B.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
C.
hasRepresentativeTitle
Indicates that an entity holds a formal title or designation that serves as its primary or most commonly used label or name.
-
D.
succeededAsSpeakerBy
Indicates that one entity took over the role or position of speaker from another entity as their successor.
-
E.
titleInEnglish
Indicates that an entity’s title or name is given in the English language.
- 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8e809881908a58c9a4e3ba07c3 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.