Triple
T4322262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Art Museum of San Francisco |
E96545
|
entity |
| Predicate | collectionSpans |
P9341
|
FINISHED |
| Object | thousands of years |
—
|
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: thousands of years | Statement: [Asian Art Museum of San Francisco, collectionSpans, thousands of years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionSpans Context triple: [Asian Art Museum of San Francisco, collectionSpans, thousands of years]
-
A.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
B.
collectionSize
Indicates the total number of items contained within a specified collection.
-
C.
numberOfSpans
Indicates the total count of distinct spans or segments associated with an entity or within a specified context.
-
D.
collectionTimespan
chosen
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
E.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351177eb88190b89fa49a88add5e8 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.