Triple
T29272073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersyankh III |
E742144
|
entity |
| Predicate | hasOfferingRoom |
P168957
|
FINISHED |
| Object | offering chapel in mastaba G 7530-7540 |
—
|
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: offering chapel in mastaba G 7530-7540 | Statement: [Mersyankh III, hasOfferingRoom, offering chapel in mastaba G 7530-7540]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfferingRoom Context triple: [Mersyankh III, hasOfferingRoom, offering chapel in mastaba G 7530-7540]
-
A.
hasOffering
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
-
B.
hasRoom
Indicates that an entity possesses, contains, or is associated with a specific room.
-
C.
hasOfferingsHall
chosen
Indicates that an entity includes or is associated with a hall or space designated for offerings.
-
D.
hasRoomService
Indicates that a lodging or accommodation offers room service as an available amenity or feature.
-
E.
hasSingleRooms
Indicates that an entity offers or includes individual rooms intended for single occupancy.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 12:48 p.m.