Triple
T751035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weeping Angels |
E15447
|
entity |
| Predicate | typicalAppearance |
P5084
|
FINISHED |
| Object | Stone statue |
—
|
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: Stone statue | Statement: [Weeping Angels, typicalAppearance, Stone statue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAppearance Context triple: [Weeping Angels, typicalAppearance, Stone statue]
-
A.
appearance
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
-
B.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
adaptationAppearance
Indicates that one entity appears or is depicted in an adaptation of another entity (such as a work being represented in a derived or reinterpreted version).
-
E.
typicalBodyType
Indicates that one entity is the usual or characteristic body type associated with 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.