Triple
T30556888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machin series |
E777721
|
entity |
| Predicate | hasCollectingAspect |
P7431
|
FINISHED |
| Object | shade varieties |
—
|
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: shade varieties | Statement: [Machin series, hasCollectingAspect, shade varieties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectingAspect Context triple: [Machin series, hasCollectingAspect, shade varieties]
-
A.
hasCollector
Indicates that an entity is associated with, or owned/curated by, a specific collector.
-
B.
hasProperCollect
Indicates that an entity is associated with a specific proper collect, i.e., a designated formal prayer or liturgical text assigned to it.
-
C.
hasAspectSystem
chosen
Indicates that an entity possesses or is associated with a particular aspect system, such as a structured set of characteristics, dimensions, or perspectives.
-
D.
hasSubAspect
Indicates that one aspect is a component, facet, or subordinate part of another broader aspect.
-
E.
hasWorkAspect
Indicates that something possesses or is characterized by a particular aspect, feature, or dimension related to work or working conditions.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a016b2629c48190befb10581560d58f |
completed | May 11, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0167d5a2088190a68dbd2b87f73e80 |
completed | May 11, 2026, 5:23 a.m. |
Created at: April 29, 2026, 8:20 p.m.