Triple
T37353347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gosselin family |
E927384
|
entity |
| Predicate | startOfPublicAttention |
P71040
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Gosselin family, startOfPublicAttention, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfPublicAttention Context triple: [Gosselin family, startOfPublicAttention, 2007]
-
A.
inceptionOfNotoriety
chosen
Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
-
B.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
C.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
D.
gainedProminenceUnder
Indicates that an entity rose to greater importance, influence, or recognition during the leadership, authority, or period associated with another entity.
-
E.
becamePublic
Indicates that an entity transitioned from private or restricted status to being publicly accessible or publicly traded.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:16 p.m.