Triple
T9443435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | registered association (eingetragener Verein) |
E227703
|
entity |
| Predicate | nameMustContain |
P9161
|
FINISHED |
| Object | suffix "eingetragener Verein" or "e.V." |
—
|
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: suffix "eingetragener Verein" or "e.V." | Statement: [registered association (eingetragener Verein), nameMustContain, suffix "eingetragener Verein" or "e.V."]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameMustContain Context triple: [registered association (eingetragener Verein), nameMustContain, suffix "eingetragener Verein" or "e.V."]
-
A.
nameRequirement
Indicates that there is a specified condition or constraint that a name must satisfy.
-
B.
fullNameIncludes
chosen
Indicates that one entity’s full name contains another specified string or name component as a substring.
-
C.
alphabetRequirement
Indicates that a specific alphabet or set of characters is required to be used in or supported by the related entity or action.
-
D.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
E.
namePattern
Indicates that an entity’s name follows or matches a specified pattern or format.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f3171248190b92ab990371e63f5 |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:51 p.m.