Triple
T5654277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum of English Rural Life |
E124578
|
entity |
| Predicate | hasArchiveSize |
P34032
|
FINISHED |
| Object | over 1 million photographs |
—
|
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: over 1 million photographs | Statement: [Museum of English Rural Life, hasArchiveSize, over 1 million photographs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchiveSize Context triple: [Museum of English Rural Life, hasArchiveSize, over 1 million photographs]
-
A.
hasSize
chosen
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
B.
hasNotableArchive
Indicates that an entity maintains or is associated with an archive that is considered significant or noteworthy.
-
C.
archivesStatus
Indicates the current archival state or condition assigned to an item, such as whether it is archived, active, or pending archiving.
-
D.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
-
E.
archiveContent
Indicates that content is being stored or moved into an archive state for long-term retention or historical reference.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022f7efec8190946c925130176d5a |
completed | March 22, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.