Triple
T38675380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian War Memorials Fund |
E943723
|
entity |
| Predicate | collectionCustodian |
P195210
|
FINISHED |
| Object | Canadian War 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: Canadian War Museum | Statement: [Canadian War Memorials Fund, collectionCustodian, Canadian War Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionCustodian Context triple: [Canadian War Memorials Fund, collectionCustodian, Canadian War Museum]
-
A.
collectorOrCustodian
chosen
Indicates that an entity serves as the collector or custodian responsible for gathering, holding, or maintaining another entity.
-
B.
catalogOwner
Indicates that one entity is the owner or controller of a particular catalog or collection of items associated with another entity.
-
C.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
D.
collectionRole
Indicates the specific function, responsibility, or position an entity holds within a collection or grouped set of items.
-
E.
collectionPoint
Indicates a location or entity designated as the place where items are gathered, received, or collected.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.