Triple
T31251974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To You, The Birdie! (Phèdre) |
E796847
|
entity |
| Predicate | companyBaseOfOrigin |
P185225
|
FINISHED |
| Object | New York City |
—
|
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: New York City | Statement: [To You, The Birdie! (Phèdre), companyBaseOfOrigin, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyBaseOfOrigin Context triple: [To You, The Birdie! (Phèdre), companyBaseOfOrigin, New York City]
-
A.
organizationCountryOfOrigin
Indicates the country where an organization was originally founded or established.
-
B.
organizationHeadquarteredInCountry
Indicates that an organization’s main headquarters or principal place of business is located within a specified country.
-
C.
workOriginatesFrom
Indicates that the creation, development, or initiation of a work can be traced back to a particular source, agent, or origin.
-
D.
countryOfUnderlyingCompany
Indicates the country in which the underlying company associated with an entity is legally established or primarily based.
-
E.
businessFoundedIn
Indicates that a business entity was established or came into existence in a specific location or time.
- F. None of above. chosen
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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 29, 2026, 9:11 p.m.