Triple
T26653472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Causeway of Khafre |
E666430
|
entity |
| Predicate | hasRelationToNile |
P195761
|
FINISHED |
| Object | linked plateau to former Nile floodplain |
—
|
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: linked plateau to former Nile floodplain | Statement: [Causeway of Khafre, hasRelationToNile, linked plateau to former Nile floodplain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationToNile Context triple: [Causeway of Khafre, hasRelationToNile, linked plateau to former Nile floodplain]
-
A.
shapeRelationToNile
Indicates how an entity’s shape is defined, influenced, or oriented in relation to the Nile River.
-
B.
joinsNile
Indicates that one river or watercourse flows into and becomes part of the Nile River.
-
C.
locatedOnBankOfNile
Indicates that something is situated on or directly adjacent to the banks of the Nile River.
-
D.
distanceFromNile
Indicates the spatial distance between a given location or entity and the Nile River.
-
E.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: April 27, 2026, 2:34 a.m.