Triple
T25898791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulwich Prep London |
E652544
|
entity |
| Predicate | hasHistoricLinksWith |
P7843
|
FINISHED |
| Object | Dulwich College |
—
|
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: Dulwich College | Statement: [Dulwich Prep London, hasHistoricLinksWith, Dulwich College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricLinksWith Context triple: [Dulwich Prep London, hasHistoricLinksWith, Dulwich College]
-
A.
hasHistoricalOrAffiliateLinkTo
Indicates that one entity is historically connected to, or has an affiliate/partnership relationship with, another entity.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHistoricalArc
Indicates that something unfolds over time in a way that forms a coherent, meaningful historical development or narrative.
-
D.
hasHistoricalTieTo
chosen
Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
-
E.
hasHistoricBasisIn
Indicates that something is grounded in, derived from, or justified by historical events, practices, or precedents.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 22, 2026, 8:23 a.m.