Triple
T36471974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ÄM 21300 |
E898559
|
entity |
| Predicate | appliesToIconicObject |
P1129
|
FINISHED |
| Object | Nefertiti Bust |
E259810
|
NE 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: Nefertiti Bust | Statement: [ÄM 21300, appliesToIconicObject, Nefertiti Bust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToIconicObject Context triple: [ÄM 21300, appliesToIconicObject, Nefertiti Bust]
-
A.
appliesToObjectType
Indicates that something (such as a rule, constraint, or operation) is specifically relevant or applicable to a particular type or class of object.
-
B.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
isIconicIn
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
D.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
E.
appliesToInteraction
Indicates that something (such as a rule, condition, or property) is relevant to or governs a specific interaction between entities.
- F. None of above.
Provenance (4 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a0944b1548190882bc5206fa8e0e4 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.