Triple
T14045762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High as Hope |
E337950
|
entity |
| Predicate | hasStrippedBackProduction |
P46648
|
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: [High as Hope, hasStrippedBackProduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrippedBackProduction Context triple: [High as Hope, hasStrippedBackProduction, true]
-
A.
canBeStrippedFor
Indicates that one entity is capable of having parts or layers removed in order to benefit, prepare, or expose another entity.
-
B.
canBeStripped
Indicates that one entity is capable of having an outer layer, covering, or component removed from it.
-
C.
hasMinimalistProduction
chosen
Indicates that something is produced or arranged using a sparse, simple, and stripped-down style with minimal elements or embellishment.
-
D.
excludesProductionsFrom
Indicates that certain productions are omitted, restricted, or not allowed in relation to a specified source or context.
-
E.
hasDenseProduction
Indicates that production activity within a given area or context is concentrated and intensive rather than sparse or dispersed.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312df37081909f45ce3e219af5dc |
completed | April 14, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.