Triple
T6949519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Ontario Museum Act |
E160883
|
entity |
| Predicate | typeOfOrganizationGoverned |
P6125
|
FINISHED |
| Object | museum |
—
|
LITERAL 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: museum | Statement: [Royal Ontario Museum Act, typeOfOrganizationGoverned, museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOrganizationGoverned Context triple: [Royal Ontario Museum Act, typeOfOrganizationGoverned, museum]
-
A.
organizationTypeGoverned
chosen
Indicates that one entity governs or has authoritative control over a specific type or category of organization.
-
B.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
C.
controlledOrganization
Indicates that one entity has the authority to direct, manage, or significantly influence the operations and decisions of another organization.
-
D.
hasMainGoverningBody
Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
-
E.
governedEntity
Indicates that one entity exercises authority, control, or governance over another entity.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.