Triple
T17130518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papasha |
E415709
|
entity |
| Predicate | associatedWithServiceEntry |
P120425
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Papasha, associatedWithServiceEntry, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithServiceEntry Context triple: [Papasha, associatedWithServiceEntry, 1941]
-
A.
serviceEntryWith
chosen
Indicates that one entity is associated with or accompanied by a particular service entry in a joint or linked context.
-
B.
linkedByServiceTo
Indicates that one entity is connected or associated with another through a specific service acting as the linking mechanism.
-
C.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
D.
associatedWithProvider
Indicates that one entity has a connection or relationship with a specific provider, such as being supplied, managed, or serviced by that provider.
-
E.
associatedWithResource
Indicates a relationship in which an entity is linked or connected to a particular resource, such that the resource is relevant or applicable to that entity.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f029d1a48190a9d4094827d11d23 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.