Triple
T32577676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adenauerplatz |
E832689
|
entity |
| Predicate | hasSignificantUse |
P70082
|
FINISHED |
| Object | public gathering place |
—
|
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: public gathering place | Statement: [Adenauerplatz, hasSignificantUse, public gathering place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantUse Context triple: [Adenauerplatz, hasSignificantUse, public gathering place]
-
A.
hasSignificant
Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
-
B.
hasPopularUse
Indicates that something is widely used, accepted, or favored by a large number of people or within a broad context.
-
C.
hasMajorUtility
Indicates that an entity possesses or is served by a primary or significant utility service (such as power, water, or gas).
-
D.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
E.
hasDominantUse
chosen
Indicates that one use or function of an entity is primary or prevailing over its other possible uses.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:04 a.m.