Triple
T38241315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden Heights |
E1013766
|
entity |
| Predicate | depictedAsHaving |
P53700
|
FINISHED |
| Object | high crime rates |
—
|
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: high crime rates | Statement: [Garden Heights, depictedAsHaving, high crime rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictedAsHaving Context triple: [Garden Heights, depictedAsHaving, high crime rates]
-
A.
believedToHave
Indicates that one entity is thought or assumed, but not confirmed, to possess or exhibit another entity or property.
-
B.
depictedAbove
Indicates that one entity is visually represented in an image, illustration, or diagram that is positioned above another referenced element in a layout or document.
-
C.
isDepictedVia
Indicates that one entity is represented, illustrated, or shown by means of another entity, such as a specific medium, style, or method of depiction.
-
D.
depicts
Indicates that one entity visually represents, portrays, or shows another entity.
-
E.
depictsAttribute
chosen
Indicates that one entity visually represents or illustrates a specific attribute or characteristic of 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:30 p.m.