Triple
T3522773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antiquities Museum |
E74462
|
entity |
| Predicate | heritageDomain |
P6203
|
FINISHED |
| Object | Egyptian archaeology |
—
|
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: Egyptian archaeology | Statement: [Antiquities Museum, heritageDomain, Egyptian archaeology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageDomain Context triple: [Antiquities Museum, heritageDomain, Egyptian archaeology]
-
A.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
B.
heritageField
chosen
Indicates that there is an association between an entity and a specific field, domain, or area related to cultural or historical heritage.
-
C.
heritageComponent
Indicates that one entity forms a constituent or contributing part of another entity’s cultural or historical heritage.
-
D.
heritageFunction
Indicates the role, use, or purpose that a heritage asset or element serves within its cultural, historical, or social context.
-
E.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4f16b8819094ad2755670ddc7b |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.