Triple
T2673717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream Stele of Thutmose IV |
E56407
|
entity |
| Predicate | describesAction |
P519
|
FINISHED |
| Object | clearing sand from around the Sphinx |
—
|
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: clearing sand from around the Sphinx | Statement: [Dream Stele of Thutmose IV, describesAction, clearing sand from around the Sphinx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesAction Context triple: [Dream Stele of Thutmose IV, describesAction, clearing sand from around the Sphinx]
-
A.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
B.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
C.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
D.
depictionAction
Indicates an action in which one entity visually represents, illustrates, or portrays another entity.
-
E.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b08b1c8190824342fc63e555d2 |
completed | March 7, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.