Triple
T37721377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle House dance studio, New York City |
E939591
|
entity |
| Predicate | notableCoOwner |
P91345
|
FINISHED |
| Object | Irene Castle |
E277927
|
NE 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: Irene Castle | Statement: [Castle House dance studio, New York City, notableCoOwner, Irene Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCoOwner Context triple: [Castle House dance studio, New York City, notableCoOwner, Irene Castle]
-
A.
notablePropertyOwnerOf
Indicates that a subject is a significant or noteworthy owner of a particular property or asset.
-
B.
coFounderNotableFor
Indicates that a person is a co-founder of something for which they are notably recognized.
-
C.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
D.
hasCoOwner
chosen
Indicates that an entity shares ownership of something with one or more other entities.
-
E.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
- F. None of above.
Provenance (4 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40e071776c819081134837ad383fa8 |
completed | June 28, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.