Triple
T13224887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of a Man with a Watch |
E314850
|
entity |
| Predicate | subjectHasAttribute |
P99469
|
FINISHED |
| Object | elegant dress |
—
|
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: elegant dress | Statement: [Portrait of a Man with a Watch, subjectHasAttribute, elegant dress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectHasAttribute Context triple: [Portrait of a Man with a Watch, subjectHasAttribute, elegant dress]
-
A.
subjectHasCharacteristic
chosen
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
-
B.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
C.
subjectHasActor
Indicates that a subject is associated with or possesses a particular actor involved in an action or process.
-
D.
hasCommunityAttribute
Indicates that a community possesses or is characterized by a specific attribute or property.
-
E.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3128348190836158467e9cfbe2 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:19 p.m.