Triple
T29970782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daoist art |
E761307
|
entity |
| Predicate | typicalWorkType |
P86785
|
FINISHED |
| Object | hanging scroll painting |
—
|
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: hanging scroll painting | Statement: [Daoist art, typicalWorkType, hanging scroll painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWorkType Context triple: [Daoist art, typicalWorkType, hanging scroll painting]
-
A.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
B.
basedOnWorkTypeOftenAppearsIn
Indicates that something of a given work type frequently appears in or is commonly found within another context or medium.
-
C.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
D.
designedTypeOfWork
Indicates that one entity is the type or category of work for which another entity was specifically designed.
-
E.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a03213d35788190bdf04e19625b4060 |
completed | May 12, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a031ea131d48190ab0fecb48b8e2205 |
completed | May 12, 2026, 12:35 p.m. |
Created at: April 29, 2026, 6:32 p.m.