Triple
T28149432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folly |
E714574
|
entity |
| Predicate | hasStrongElement |
P192832
|
FINISHED |
| Object | landscapeDescription |
—
|
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: landscapeDescription | Statement: [Folly, hasStrongElement, landscapeDescription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongElement Context triple: [Folly, hasStrongElement, landscapeDescription]
-
A.
hasStrongField
Indicates that one entity possesses or exhibits a powerful or intense field (such as a physical, electromagnetic, or influence field) relative to some context or standard.
-
B.
hasBruteElement
Indicates that an entity possesses or is associated with a raw, force-based, or brute-type elemental property.
-
C.
hasMainElements
Indicates that something possesses or is composed of its primary or most important constituent parts.
-
D.
hasStrongLanguage
Indicates that the subject contains or uses intense, offensive, or explicit language.
-
E.
hasStrengthDescriptor
Indicates that an entity is associated with a qualitative description of its strength or intensity.
- F. None of above. chosen
Provenance (4 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: April 27, 2026, 9:58 p.m.