Triple
T13692496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Physical Energy |
E328299
|
entity |
| Predicate | hasMonumentalScale |
P60650
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Physical Energy, hasMonumentalScale, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonumentalScale Context triple: [Physical Energy, hasMonumentalScale, true]
-
A.
hasLargeScale
chosen
Indicates that an entity operates, exists, or is implemented at a large or extensive scale relative to typical or baseline cases.
-
B.
isMonumentalTree
Indicates that a tree is officially recognized as exceptionally significant, typically due to its age, size, rarity, historical, cultural, or ecological importance.
-
C.
isMonumentClassic
Indicates that a monument exemplifies classic or traditional architectural or historical style.
-
D.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
E.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.