Triple
T3335401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Street, Berlin |
E70128
|
entity |
| Predicate | usesFormCharacteristic |
P47980
|
FINISHED |
| Object | distorted forms |
—
|
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: distorted forms | Statement: [Street, Berlin, usesFormCharacteristic, distorted forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFormCharacteristic Context triple: [Street, Berlin, usesFormCharacteristic, distorted forms]
-
A.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
B.
formsFeature
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
C.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
D.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
E.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb197bd0481909a5cf7eab386e176 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69adaa518ac88190b64f949ace018ab7 |
completed | March 8, 2026, 4:56 p.m. |
Created at: March 8, 2026, 3:12 p.m.