Triple
T22423589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mastaba G 4140 |
E554308
|
entity |
| Predicate | associatedWithTitleOfOccupant |
P5175
|
FINISHED |
| Object | queen consort |
—
|
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: queen consort | Statement: [Mastaba G 4140, associatedWithTitleOfOccupant, queen consort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTitleOfOccupant Context triple: [Mastaba G 4140, associatedWithTitleOfOccupant, queen consort]
-
A.
associatedWithTitleHolderRole
Indicates a relationship where an entity is connected to, or linked with, a role held by a title holder.
-
B.
intendedOccupant
Indicates that one entity is designated or meant to be the occupant of another entity (such as a space, seat, or dwelling).
-
C.
jurisdictionOfOccupant
Indicates the legal authority or control that an occupant exercises over a place, property, or domain.
-
D.
associatedTitle
chosen
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
E.
positionAssociatedWith
Indicates a relationship where a specific role, job, or position is linked or connected to a particular entity, context, or resource.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2af620819083338127e78137dc |
completed | April 29, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.