Triple
T23986620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenford |
E604956
|
entity |
| Predicate | hasNotableCompanyHistory |
P61859
|
FINISHED |
| Object | J. Lyons and Co. |
—
|
NE NERFINISHED |
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: J. Lyons and Co. | Statement: [Greenford, hasNotableCompanyHistory, J. Lyons and Co.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCompanyHistory Context triple: [Greenford, hasNotableCompanyHistory, J. Lyons and Co.]
-
A.
hasNotableCompany
Indicates that an entity is associated with or linked to a company that is considered notable or significant in some context.
-
B.
notableCompanyHistory
chosen
Indicates that there exists a significant or historically important relationship or event involving the company and the subject entity.
-
C.
hasNotableHistoricalAssociation
Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
-
D.
hasMajorShareholderHistory
Indicates that an entity has had one or more major shareholders at some point in its history.
-
E.
hasUnderlyingCompanyWellKnownFor
Indicates that an entity is associated with an underlying company that is widely recognized or notable.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2c1d4508190905a3eb2d98a248b |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:36 p.m.