Triple
T687674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresno Art Museum |
E13318
|
entity |
| Predicate | hasCollectionScope |
P397
|
FINISHED |
| Object | regional art |
—
|
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: regional art | Statement: [Fresno Art Museum, hasCollectionScope, regional art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionScope Context triple: [Fresno Art Museum, hasCollectionScope, regional art]
-
A.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
B.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
C.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
-
D.
hasCollectionItemBy
Indicates that an entity possesses or includes a specific item as part of its collection, identified or referenced by some key or identifier.
-
E.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.