Triple
T29773734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Colchester |
E755318
|
entity |
| Predicate | hasMuseumCollectionsIn |
P32052
|
FINISHED |
| Object | Colchester Castle Museum |
—
|
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: Colchester Castle Museum | Statement: [Roman Colchester, hasMuseumCollectionsIn, Colchester Castle Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMuseumCollectionsIn Context triple: [Roman Colchester, hasMuseumCollectionsIn, Colchester Castle Museum]
-
A.
hasMuseumComponent
Indicates that something includes, contains, or is composed of a museum or museum-related part as one of its components.
-
B.
hasMuseumFunction
Indicates that an entity serves the role or performs the function of a museum.
-
C.
museumHolds
chosen
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
D.
hasMuseumCollectionFocus
Indicates that a museum collection is primarily centered on, dedicated to, or thematically focused around a particular subject, type of object, or area of interest.
-
E.
hasMuseumOrTreasureHouse
Indicates that an entity contains, hosts, or is associated with a museum or treasure house.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 8:44 p.m.