Triple
T33172455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue du Sentier |
E849069
|
entity |
| Predicate | hasRecentRole |
P204227
|
FINISHED |
| Object | cluster for digital startups |
—
|
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: cluster for digital startups | Statement: [Rue du Sentier, hasRecentRole, cluster for digital startups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecentRole Context triple: [Rue du Sentier, hasRecentRole, cluster for digital startups]
-
A.
hasPastMemberRole
Indicates that an entity previously held, but no longer holds, a specified member role within a group or organization.
-
B.
hasLaterRole
Indicates that an entity holds or assumes a role that occurs after another role in time or sequence.
-
C.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
D.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
E.
hasRecurringRole
Indicates that an entity repeatedly appears or participates in a role within an ongoing or multiple related contexts over 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a035052a47081908e9e56e21c543d46 |
completed | May 12, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_6a034d306e588190a2dce906fd46eb54 |
completed | May 12, 2026, 3:54 p.m. |
| PDg | Predicate description generation | batch_6a035051a02481909e2a6868f9253a92 |
completed | May 12, 2026, 4:07 p.m. |
Created at: May 1, 2026, 1:29 a.m.