Triple
T19687681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Purgatory |
E472753
|
entity |
| Predicate | terracesCorrespondTo |
P134497
|
FINISHED |
| Object | Pride |
—
|
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: Pride | Statement: [Mount Purgatory, terracesCorrespondTo, Pride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terracesCorrespondTo Context triple: [Mount Purgatory, terracesCorrespondTo, Pride]
-
A.
terracesSymbolize
chosen
Indicates that terraces serve as symbols or representations of certain ideas, values, or meanings within a given context.
-
B.
numberOfTerraces
Indicates the total count of terraces associated with a given entity.
-
C.
formsTerraceWith
Indicates that one entity combines or aligns with another to create or constitute a terrace-like structure or formation.
-
D.
usedTerracing
Indicates that an entity employed terracing techniques, such as creating stepped or leveled surfaces, in carrying out an activity or modifying land.
-
E.
hasTerracesFromPeriod
Indicates that an entity possesses terraces that were constructed or are associated with a specific historical or chronological period.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420d39688190ad3a84dbffce4ffe |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.