Triple
T311954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Pyramid |
E7626
|
entity |
| Predicate | entranceLocation |
P1974
|
FINISHED |
| Object | north face |
—
|
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: north face | Statement: [Red Pyramid, entranceLocation, north face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceLocation Context triple: [Red Pyramid, entranceLocation, north face]
-
A.
hasEntranceOn
chosen
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
B.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
hasNumberOfEntrances
Indicates the relationship that specifies how many entrances an entity possesses.
-
D.
firstLocation
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
-
E.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.