Triple
T33269762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptologists |
E851744
|
entity |
| Predicate | curate |
P176440
|
FINISHED |
| Object | Egyptian collections |
—
|
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 collections | Statement: [Egyptologists, curate, Egyptian collections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curate Context triple: [Egyptologists, curate, Egyptian collections]
-
A.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
B.
curatesArchiveOf
Indicates that one entity is responsible for organizing, maintaining, and managing the archival collection belonging to another entity.
-
C.
curatedIn
Indicates that an entity has been intentionally selected, organized, or managed for inclusion within a particular collection, exhibition, or curated context.
-
D.
curatesArchivesOf
Indicates that one entity is responsible for organizing, managing, and maintaining the archival materials belonging to another entity.
-
E.
coCuratedWith
Indicates that two or more entities have been jointly curated or organized together as part of the same curation activity or process.
- F. None of above. chosen
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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:32 a.m.