Triple
T33520276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundling Hospital |
E858479
|
entity |
| Predicate | notableWorkPreservedAt |
P21692
|
FINISHED |
| Object | Foundling Museum |
E244013
|
NE 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: Foundling Museum | Statement: [Foundling Hospital, notableWorkPreservedAt, Foundling Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkPreservedAt Context triple: [Foundling Hospital, notableWorkPreservedAt, Foundling Museum]
-
A.
notableWorkContained
Indicates that a notable work is included within or is part of another entity, such as a collection, publication, or compilation.
-
B.
workPreservedIn
chosen
Indicates that a work is maintained, stored, or archived within a particular medium, collection, or repository so that it remains accessible over time.
-
C.
notableWorkPublicationDate
Indicates the date on which a notable work associated with an entity was first published.
-
D.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
E.
notableWorkBacked
Indicates that a notable work has been supported, endorsed, or financially backed by a particular entity.
- F. None of above.
Provenance (4 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a361184ccfc819085cbe0b188c10b5f |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:39 a.m.