Triple
T3546238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahun Pyramid |
E75002
|
entity |
| Predicate | hasCauseway |
P27773
|
FINISHED |
| Object | causeway leading to valley area |
—
|
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: causeway leading to valley area | Statement: [Lahun Pyramid, hasCauseway, causeway leading to valley area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCauseway Context triple: [Lahun Pyramid, hasCauseway, causeway leading to valley area]
-
A.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
B.
hasPathway
chosen
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
-
C.
hasSkyway
Indicates that there is an elevated, usually enclosed walkway or bridge connecting two or more structures or areas.
-
D.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
E.
hasViaduct
Indicates that one entity possesses, includes, or is connected by a viaduct in relation to another entity.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfcf64488190af8452308734028c |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.