Triple
T31402698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudkøbing Municipality |
E801042
|
entity |
| Predicate | formedNewEntity |
P135839
|
FINISHED |
| Object | Langeland Municipality |
—
|
NE NERFINISHED |
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: Langeland Municipality | Statement: [Rudkøbing Municipality, formedNewEntity, Langeland Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedNewEntity Context triple: [Rudkøbing Municipality, formedNewEntity, Langeland Municipality]
-
A.
createdEntityProposed
Indicates that an entity has been brought into existence in a suggested, draft, or not-yet-finalized form.
-
B.
createdEntityType
Indicates the type or category of entity that was produced or brought into existence as a result of the creation action.
-
C.
formsEntity
Indicates that one entity creates, shapes, or constitutes another entity as a result or outcome.
-
D.
definesEntity
Indicates that one entity specifies, determines, or establishes the identity, nature, or boundaries of another entity.
-
E.
newPoliticalEntity
chosen
Indicates the creation or establishment of a new political unit or organization as a distinct entity.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 29, 2026, 9:20 p.m.