Triple
T37721375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle House dance studio, New York City |
E939591
|
entity |
| Predicate | coRunBy |
P7944
|
FINISHED |
| Object | Irene Castle |
—
|
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: Irene Castle | Statement: [Castle House dance studio, New York City, coRunBy, Irene Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRunBy Context triple: [Castle House dance studio, New York City, coRunBy, Irene Castle]
-
A.
runBy
chosen
Indicates that an entity is operated, managed, or controlled by another entity.
-
B.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
-
C.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
D.
runsByDefault
Indicates that an action, process, or behavior is executed automatically without requiring explicit configuration or invocation.
-
E.
alsoRuns
Indicates that the subject, in addition to its primary or previously mentioned activity or role, performs or operates another activity, process, or 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.