Triple
T17232014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirschfeld on Line |
E418262
|
entity |
| Predicate | featuresWorkType |
P126481
|
FINISHED |
| Object | illustrations |
—
|
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: illustrations | Statement: [Hirschfeld on Line, featuresWorkType, illustrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresWorkType Context triple: [Hirschfeld on Line, featuresWorkType, illustrations]
-
A.
featureTypeCatalog
Indicates that an entity is associated with, or defined by, a catalog that specifies the types of features it can include or reference.
-
B.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
C.
featuresOrchestrationBy
Indicates that something (such as a work, event, or performance) is characterized by or includes orchestration carried out by a particular agent or entity.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
- F. None of above. chosen
Provenance (4 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42df7da748190a3a1762a67eb871b |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:39 a.m.