Triple
T10936679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blonde |
E258350
|
entity |
| Predicate | visualMarker |
P32310
|
FINISHED |
| Object | striking physical beauty |
—
|
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: striking physical beauty | Statement: [The Blonde, visualMarker, striking physical beauty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualMarker Context triple: [The Blonde, visualMarker, striking physical beauty]
-
A.
visionOrSign
Indicates a relationship where something is perceived or presented as a vision, sign, or symbolic manifestation, often conveying a message, omen, or divine indication.
-
B.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
C.
visualCenterpiece
Indicates that one entity serves as the primary visual focus or dominant visual element in relation to another entity.
-
D.
distinctiveMarking
chosen
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
E.
vision
Indicates that an entity perceives another entity or object visually, using sight.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770afaa1c8190b8fced9c694c0938 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.