Triple
T29272074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersyankh III |
E742144
|
entity |
| Predicate | hasFalseDoor |
P181145
|
FINISHED |
| Object | false door stela in tomb 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: false door stela in tomb G 7530-7540 | Statement: [Mersyankh III, hasFalseDoor, false door stela in tomb G 7530-7540]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFalseDoor Context triple: [Mersyankh III, hasFalseDoor, false door stela in tomb G 7530-7540]
-
A.
hasNumberOfFalseDoors
Indicates that an entity is associated with a specific count of false doors (door-like architectural features that do not function as actual entrances or exits).
-
B.
hasStageDoor
Indicates that a venue or building possesses a dedicated stage door used for performers and staff to access backstage areas.
-
C.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
D.
hasSecretExits
Indicates that an entity possesses one or more hidden or concealed exits that are not part of its normal, visible access points.
-
E.
hasSecretExit
Indicates that something includes or is connected to a hidden or concealed way out.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 28, 2026, 12:48 p.m.