Triple
T31733886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Forbes |
E809934
|
entity |
| Predicate | notableCollectionType |
P74159
|
FINISHED |
| Object | historical artifacts |
—
|
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: historical artifacts | Statement: [Christopher Forbes, notableCollectionType, historical artifacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCollectionType Context triple: [Christopher Forbes, notableCollectionType, historical artifacts]
-
A.
notableCollectionFrom
Indicates that one entity is a significant or noteworthy collection originating from, or sourced from, another entity.
-
B.
notableCollectionIncludes
Indicates that a notable or significant collection contains or features the specified item as one of its components.
-
C.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
D.
notableCategoryType
chosen
Indicates that an entity is notably associated with or classified under a particular category type.
-
E.
notableCollectionGenre
Indicates that a collection is recognized as notable specifically within a given genre.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:22 p.m.