Triple
T10275300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labná |
E240948
|
entity |
| Predicate | hasIconicView |
P3894
|
FINISHED |
| Object | arch with temple on pyramid in background |
—
|
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: arch with temple on pyramid in background | Statement: [Labná, hasIconicView, arch with temple on pyramid in background]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconicView Context triple: [Labná, hasIconicView, arch with temple on pyramid in background]
-
A.
hasIconicElement
Indicates that something contains or features a distinctive, widely recognized element that symbolizes its identity or significance.
-
B.
hasIconicModel
Indicates that something is associated with or represented by a particularly famous or emblematic model.
-
C.
hasIconicArea
Indicates that an entity possesses a distinct, widely recognized area or region that is emblematic or characteristic of it.
-
D.
hasIconicStructure
chosen
Indicates that an entity possesses a structure or feature that is widely recognized as emblematic or symbolically representative of it.
-
E.
isIconicIn
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d28b6cd4819084a7a5c1893b5ad8 |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:37 a.m.