Triple
T30396597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susanna Dickinson |
E773234
|
entity |
| Predicate | messageTopic |
P166147
|
FINISHED |
| Object | fall of the Alamo |
—
|
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: fall of the Alamo | Statement: [Susanna Dickinson, messageTopic, fall of the Alamo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageTopic Context triple: [Susanna Dickinson, messageTopic, fall of the Alamo]
-
A.
subjectOfMessages
chosen
Indicates that an entity is the main topic or focus about which the messages are written or communicated.
-
B.
messageSpace
Indicates a relationship where one entity provides or occupies a space or channel through which messages can be sent, stored, or exchanged between parties.
-
C.
exampleTopic
Indicates that something serves as an illustrative or representative instance of a broader topic or concept.
-
D.
legacyTopic
Indicates that a topic or subject is considered outdated, superseded, or retained only for backward compatibility or historical reasons.
-
E.
documentationTopic
Indicates that one entity serves as the subject or focus of documentation related to another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685add1a48190b59d888f861cd410 |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:02 p.m.