Triple
T13913760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feuerschutzpolizei |
E334563
|
entity |
| Predicate | absorbedFrom |
P73100
|
FINISHED |
| Object | local municipal fire departments |
—
|
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: local municipal fire departments | Statement: [Feuerschutzpolizei, absorbedFrom, local municipal fire departments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absorbedFrom Context triple: [Feuerschutzpolizei, absorbedFrom, local municipal fire departments]
-
A.
absorbed
Indicates that one entity takes in, soaks up, or assimilates another entity or substance.
-
B.
adoptedFrom
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
-
C.
incorporatedFrom
chosen
Indicates that one entity was formed, established, or legally created by deriving or transforming from another pre-existing entity.
-
D.
integratedFrom
Indicates that something has been formed or constructed by combining or incorporating elements originating from another source.
-
E.
ownedFrom
Indicates that ownership of an entity began or was acquired starting from a specified time or source.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27245c648190b2946845ce0fdbf8 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.