Triple
T33645591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Row |
E861951
|
entity |
| Predicate | foundedBySiblingDuo |
P47720
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Row, foundedBySiblingDuo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedBySiblingDuo Context triple: [The Row, foundedBySiblingDuo, true]
-
A.
foundedByFamily
Indicates that an organization, institution, or entity was established by one or more members of the same family.
-
B.
foundedBySiblingTeam
chosen
Indicates that an entity (such as an organization, project, or venture) was established by a team composed of siblings working together as co-founders.
-
C.
foundedByCoFounderOf
Indicates that an entity was founded by a person who is also a co-founder of another entity.
-
D.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 1:42 a.m.