Triple
T9132064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ma Rainey |
E219108
|
entity |
| Predicate | touringCircuit |
P56890
|
FINISHED |
| Object | vaudeville circuit |
—
|
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: vaudeville circuit | Statement: [Ma Rainey, touringCircuit, vaudeville circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touringCircuit Context triple: [Ma Rainey, touringCircuit, vaudeville circuit]
-
A.
touringActivity
Indicates an activity where an entity travels from place to place, typically for visiting, performing, or sightseeing purposes.
-
B.
touringScope
chosen
Indicates the extent or range of locations, venues, or areas covered by an entity’s tour or touring activity.
-
C.
touringArea
Indicates that an entity is designated as an area or region where touring or guided visits take place.
-
D.
continuedTouringAfter
Indicates that one entity persisted in touring or traveling for performances or events after another specified time, event, or entity’s touring activity.
-
E.
touringStyle
Indicates the manner or approach in which an entity conducts or experiences a tour (e.g., type, format, or style of touring).
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8db7d808190bd22b0e5a6f9c285 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.