Triple
T4164921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John W. Parker and Son |
E84421
|
entity |
| Predicate | geographicAreaOfActivity |
P82
|
FINISHED |
| Object | London publishing scene |
—
|
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: London publishing scene | Statement: [John W. Parker and Son, geographicAreaOfActivity, London publishing scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicAreaOfActivity Context triple: [John W. Parker and Son, geographicAreaOfActivity, London publishing scene]
-
A.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
B.
continentOfActivity
Indicates the continent on which an entity primarily operates, is active, or conducts its main activities.
-
C.
placeOfBusinessActivity
Indicates the type or nature of business activity that is conducted at a particular place or location.
-
D.
arealRegion
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
-
E.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.